Bitcoin mempool

Every node maintains its own mempool — the queue of unconfirmed transactions waiting to be included in a block. This page shows ours right now: how many txs, total weight, the distribution of fee rates they're bidding, and what Bitcoin Core's estimatesmartfee projects for common confirmation targets. For state-classified live fee pressure (Low/Moderate/High/Severe), see /reports/fee-pressure.

Unconfirmed transactions

12,182

Total weight

5.2 M vB

~5.2 blocks of backlog (1 MvB per block)

Total fees offered

0.1628 BTC

if every tx confirmed at its current rate

Confirmation-target fee estimates

From Bitcoin Core's estimatesmartfee, which models recent block-inclusion rates per fee bucket and returns the lowest fee that would have confirmed within the target. Always returns a number; if the mempool is empty, the floor of 1 sat/vB applies.

Next block (~10 min)

5 sat/vB

target: 1 block

~½ hour

4 sat/vB

target: 3 blocks

~1 hour

4 sat/vB

target: 6 blocks

Fee-rate distribution

All 12,182 pending txs bucketed by their fee rate in sat/vB. Bar height: number of transactions in each band. Hover for the corresponding total vsize.

Mempool size over time

Snapshotted every 10 minutes from getmempoolinfo since 2026-05-12. Mempool is local node state, not on-chain — there's no way to reconstruct history from before we started observing.

Looking for the long-term story?

Mempool depth (tx count waiting) and fee pressure (sat/vB needed to confirm) track the same underlying phenomenon — chain congestion — but fee pressure is what users actually experience. It's also recoverable from on-chain data going back to genesis, because every confirmed block records the fees it accepted.

For "how busy was the chain in [past period]?" — fee-pressure history is the better answer.

Fee pressure: complete history →