The Mempool Explained — Bitcoin's Waiting Room for Transactions

The Mempool Explained

When you send a Bitcoin transaction, it doesn't go straight into a block. It enters the mempool — a holding area of unconfirmed transactions that every node maintains. Understanding the mempool is essential for anyone who wants to optimize fees and confirmation times.

What is the Mempool?

Technically, there's no single mempool. Every Bitcoin node maintains its own set of unconfirmed transactions. These overlap significantly but aren't identical — your node might see a transaction before mine does. When people say "the mempool," they usually mean the aggregate view from well-connected nodes.

Mempool Mechanics

• Default size: 300 MB (configurable). When full, lowest-fee transactions are dropped
• Transaction validation: Nodes validate every transaction before accepting it into their mempool
• Expiration: Transactions expire from the mempool after ~2 weeks if not confirmed
• Propagation: New transactions propagate across the network in seconds via the gossip protocol

The Fee Market

Miners select transactions from the mempool to include in their blocks. Naturally, they pick the highest-fee transactions first. This creates a real-time auction for block space.

Fee rates are measured in satoshis per virtual byte (sat/vB). A typical transaction is 140-250 vB. During quiet periods, 1-2 sat/vB gets you into the next block. During congestion (like after the Ordinals mania), fees can spike to 100+ sat/vB.

Fee Estimation

Wallets estimate appropriate fees by looking at the current mempool state. Better wallets show you the mempool visually so you can choose your priority level. I recommend checking mempool.space before any significant transaction.

RBF — Replace-By-Fee

RBF (BIP 125) lets you bump the fee on an unconfirmed transaction by creating a new version with a higher fee. The new transaction spends the same inputs but pays more, so miners prefer it. This is essential when you underestimate fees.

Full RBF (where any unconfirmed transaction can be replaced, regardless of signaling) was enabled by default in Bitcoin Core 26.0. This is a pragmatic change — it acknowledges that unconfirmed transactions were never truly "final."

CPFP — Child Pays for Parent

What if you're the recipient and the sender used a low fee? You can't RBF their transaction, but you can create a child transaction spending the output of the stuck parent, with a high enough fee to incentivize miners to confirm both together.

Miners evaluate "packages" of transactions. If the parent + child combined fee rate is attractive, they'll mine both. This is called package relay, and it's been improved significantly in recent Bitcoin Core versions.

Practical Tips

1. Always check mempool.space before sending a transaction
2. Use wallets that support RBF by default (most modern wallets do)
3. During high-fee periods, batch transactions to save on fees
4. Use SegWit addresses (bc1...) for lower fees vs legacy addresses
5. For non-urgent transfers, set a low fee and wait — weekends are typically cheaper

The mempool is Bitcoin's free market in its purest form. No price controls, no subsidies, no favoritism. You bid for block space, and the market clears.

Monitor the mempool in real-time with tools on our tools page.