The pending transaction queue
Mempool
Pending transaction count, queue depth, fee-rate distribution and the blocks the mempool would currently produce.
Queue state
Everything waiting to be confirmed.
Fee-rate distribution
Where the competition actually is.
Transactions compete for blockspace by fee rate, not by size or value. This is how much pending virtual size sits in each fee band — which is what decides whether your own rate confirms.
Loading fee distribution…
Projected blocks
The next blocks, as the queue stands.
If mining stopped accepting new transactions right now, these are the blocks the current mempool would produce, in order.
Loading projected blocks…
Reading this page
What the mempool is, and is not.
There is no single mempool
Every node keeps its own view of unconfirmed transactions, shaped by when it saw them and by its own relay policy. The figures here come from one well-connected node’s view. Another node will differ slightly, and neither is wrong.
Virtual size, not byte size
Blockspace is measured in virtual bytes, which discount witness data introduced by SegWit. That is why a block is described as roughly 1 vMB even though it can carry more raw data, and why fee rates are quoted in sat/vB.