BITCOIN MAINNETLive explorer status
BEFORE THE NEXT BLOCK

Bitcoin mempool, live.

Explore pending Bitcoin transactions and their fees. Mempool observations can differ across the network.

Pending transactions
Observed pending transactions
Virtual size
16.62 MB
Sum of transaction virtual sizes
Network status
Connected
54 peers
LIVE MEMPOOL

Pending transactions

25 per page · ordered by transaction ID · first page refreshes every 30 seconds

32,321 transactions at snapshotSnapshot
Transaction IDFee · satsFee rate · sat/vBVirtual sizeFirst seen · UTCDetails
130.103126 vB
150.120125 vB
150.120125 vB
150.120125 vB
130.103126 vB
150.119126 vB
130.103126 vB
1520.1011,505 vB
130.103126 vB
130.103126 vB
130.103126 vB
150.120125 vB
150.120125 vB
260.206126 vB
130.103126 vB
170.121140 vB
1841.673110 vB
130.103126 vB
130.103126 vB
150.120125 vB
150.119126 vB
150.120125 vB
150.120125 vB
130.103126 vB
150.119126 vB
Page 1 of 1,293 · 32,321 browsable

Fees are shown as exact satoshi amounts; fee rates are rounded to three decimals. First seen is when this explorer observed the transaction, not its first broadcast across Bitcoin. Values were checked . A transaction may confirm, be replaced, conflict, or be evicted after this snapshot.

Is this the entire network’s mempool?

No. Every node has its own mempool. Connectivity, relay policy and capacity affect which transactions it sees and retains.

Why can a pending transaction disappear?

It may have confirmed, been replaced, conflicted with another transaction, or been evicted. Absence from this node alone does not establish what happened.