Bitcoin Mempool Explained: Where Transactions Compete

The Bitcoin mempool is a temporary holding area where unconfirmed transactions wait before being added to the blockchain. When you send Bitcoin, your transaction enters the mempool, gets sorted by fee priority, and is eventually picked up by miners for confirmation.

But not all transactions move through the mempool smoothly. Some get delayed, others get dropped, and during busy periods, fees can spike unpredictably. Understanding how the mempool works is key to knowing why these issues happen and how to avoid them.

What Is the Bitcoin Mempool?

Every Bitcoin node maintains its own mempool, meaning different nodes may have slightly different sets of pending transactions at any given time.

This system exists because Bitcoin blocks have limited capacity (currently capped at ~4 million weight units) and are created roughly every 10 minutes, so not all transactions can be confirmed immediately.

You can think of the mempool as a constantly changing list of pending transactions – growing when network activity is high and shrinking as new blocks are mined.

How the Bitcoin Mempool Works

Step 1: Entry

A transaction enters the mempool after it is created, signed, and broadcast to the Bitcoin network. Nodes that receive it first verify that it follows the Bitcoin consensus rules (valid signature, no double-spending, correct format).

If it passes, they store it in their mempool.

Example:

You send 0.01 BTC and attach a fee rate of 20 sat/vB. When your wallet broadcasts this transaction:

• A nearby node receives it
• It checks that your inputs are valid (you actually own the BTC)
• If everything is correct, it adds your transaction to its mempool

Within a few seconds, other nodes also receive and validate the same transaction, so it starts appearing across the network – even though it hasn’t been confirmed yet.

Step 2: Sorting & Storage

Once inside the mempool, transactions are organized mainly by fee rate (sat/vB). Higher-fee transactions are more attractive to miners, so they are effectively placed “closer to the front of the line.”

Each node stores these transactions locally in memory (hence the name “memory pool”), and the exact contents can differ slightly between nodes depending on what they’ve received and accepted.

Step 3: Propagation

Transactions don’t stay on just one node – they are shared across the peer-to-peer network. When a node accepts a transaction, it forwards it to other nodes, which repeat the same validation process.

This propagation is why your transaction quickly becomes visible across the network (and on tools like mempool explorers), even before it’s confirmed.

Step 4: Size Management

The mempool is not unlimited. Each node sets a maximum size (commonly around 300 MB by default in Bitcoin Core).

When the mempool gets too full:

• Nodes start dropping (evicting) low-fee transactions
• They may also reject new transactions that don’t meet a minimum fee threshold

This creates a natural filtering system where only the most competitive (higher-fee) transactions remain during busy periods.

Step 5: Exit

A transaction leaves the mempool in two main ways:

1. Confirmation: A miner selects it, includes it in a block, and it becomes part of the blockchain. Once the block is added, the transaction is removed from mempools across the network.
2. Removal (drop/expiry): If the transaction has a very low fee or stays unconfirmed for too long, it may be removed from the mempool to free up space.

In simple terms, transactions either get confirmed – or they get pushed out if they can’t compete.

If you want to understand what happens before and after this stage, you can explore the full process in this guide.

Why Bitcoin Transactions Get Stuck

1. Block size/weight limit → Not enough space

Bitcoin blocks have a limited capacity of ~4 million weight units (roughly equivalent to 1-2 MB depending on transaction types). This means only a limited number of transactions can be included in each block.

Since blocks are added to the blockchain at a fixed rate, the network can only process a certain number of transactions per second. When more transactions are submitted than can fit into blocks, the extra ones remain in the mempool and start to queue up.

2. Mempool congestion (high demand)

During busy periods, such as market volatility or NFT/Ordinal activity on Bitcoin, the number of new transactions can spike significantly.

Example:

In May 2023, during the surge of Bitcoin Ordinals activity, the Bitcoin mempool exceeded 400,000 unconfirmed transactions at its peak. This created a backlog that took several days to fully clear, even as new blocks continued to be mined.

When this happens, even normal-fee transactions may experience delays simply because there are too many transactions competing for limited block space.

3. Mempool eviction (transactions get dropped)

Each node limits how much memory it allocates to its mempool (commonly around 300 MB by default in Bitcoin Core). When this limit is reached, nodes begin removing the lowest-fee transactions to make room for new ones.

If your transaction gets dropped:

• It may disappear from mempool explorers
• It can return to your wallet as “unconfirmed”
• You may need to resend it with a higher fee

4. Low-fee transactions get “outbid”

When many transactions are waiting, those with higher fees are more likely to be included first. If your transaction has a low fee, it can be pushed further down the queue as newer, higher-fee transactions arrive.

Example:

• You send a transaction with 10 sat/vB
• Later, many users send transactions at 30-50 sat/vB

Miners will prioritize the higher-fee ones, so your transaction may stay in the mempool much longer – even if it was submitted earlier.

>> Related: What Is Bitcoin Mining? How New BTC Enters Circulation

How Fee Priority Works in the Bitcoin Mempool

Miners typically fill each block with the highest-fee-rate transactions available, which creates a natural ranking system inside the mempool.

To make this easier to understand, mempool data is often grouped into four practical fee tiers based on how quickly a transaction is likely to be confirmed:

Imagine the mempool currently has:

• 200,000 pending transactions
• Most of them paying 30–60 sat/vB

If you submit a transaction at:

• 55 sat/vB → likely included in the next block
• 25 sat/vB → may wait a few blocks
• 5 sat/vB → could be delayed for hours or longer

These ranges change depending on network demand. Even if your fee looks “high” at the moment you send the transaction, it can quickly become low if new, higher-fee transactions enter the mempool after you.

Why the Mempool Matters Beyond Your Transaction

When the mempool grows, it signals that demand for block space is high, which usually leads to higher transaction fees and longer confirmation times. On the other hand, a nearly empty mempool often means transactions can be confirmed quickly with lower fees.

This makes the mempool a useful tool for:

• Estimating fees: Wallets use mempool data to suggest how much you should pay to get confirmed within a certain time
• Reading market activity: Sudden spikes in mempool size often happen during price volatility or major on-chain events
• Understanding network health: A consistently congested mempool can indicate sustained demand for Bitcoin block space

How to Check the Bitcoin Mempool

One of the most widely used tools is Mempool.space. It provides a visual chart of the mempool, showing how many transactions are waiting and how they are grouped by fee rate.

Another option is Blockchain.com Explorer, which also lets you track individual transactions and view their confirmation status.

When using these tools, here’s what to look for:

• Mempool size: A larger mempool usually means more congestion
• Fee bands (sat/vB): Shows what fee rates are currently being prioritized
• Next block estimate: Indicates the fee needed for fast confirmation

Example: If a mempool chart shows that most transactions in the next block are paying 40–60 sat/vB, setting your fee within that range gives you a high chance of quick confirmation. If you choose 10 sat/vB, your transaction will likely wait until the network becomes less busy.

Conclusion

A useful way to look at the Bitcoin mempool is as a real-time pricing layer for Bitcoin block space, rather than just a waiting area. With that perspective, decisions around transactions become more deliberate.

Instead of relying only on default fee suggestions, you can time your transactions based on network conditions and choose fee levels more strategically. This helps reduce unnecessary costs and lowers the chance of delays, especially during periods of high congestion.