You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes a transaction you would have mined doesn't get mined in the next block.
Sometimes the block contains even higher fee transactions that you weren't aware of. Sometimes the block is smaller than the maximum size and the excluded one didn't just meet the cutoff, and sometimes the transaction was excluded in favour of lower paying transactions (did the miner not know of the missed transaction, was the miner being paid under the table for some they did include, .or is something more interesting going on?).
An example of other interesting things that might be noticed could include transaction censorship (is a miner choosing to not mine a particular user's), or an undisclosed softfork by some miners.
This is closely related and relevant to the compact block reconstruction hitrate which is important for block propagation performance.
Because of CPFP and whatnot, it might not be trivial to get a consistent metric for charting. One possible way would be to consider a union of all txn in the block and create a block template with the blocks actual size (minus the coinbase) and it should have equal or higher fees... and see what transactions got included that the miner left out, or got included that the miner left in.
If you do have a notion of which transactions should have been included but weren't, you could also chart how long they'd been in your local mempool.
The text was updated successfully, but these errors were encountered:
Sometimes a transaction you would have mined doesn't get mined in the next block.
Sometimes the block contains even higher fee transactions that you weren't aware of. Sometimes the block is smaller than the maximum size and the excluded one didn't just meet the cutoff, and sometimes the transaction was excluded in favour of lower paying transactions (did the miner not know of the missed transaction, was the miner being paid under the table for some they did include, .or is something more interesting going on?).
An example of other interesting things that might be noticed could include transaction censorship (is a miner choosing to not mine a particular user's), or an undisclosed softfork by some miners.
This is closely related and relevant to the compact block reconstruction hitrate which is important for block propagation performance.
Because of CPFP and whatnot, it might not be trivial to get a consistent metric for charting. One possible way would be to consider a union of all txn in the block and create a block template with the blocks actual size (minus the coinbase) and it should have equal or higher fees... and see what transactions got included that the miner left out, or got included that the miner left in.
If you do have a notion of which transactions should have been included but weren't, you could also chart how long they'd been in your local mempool.
The text was updated successfully, but these errors were encountered: