BTC—ETH—SOL—XRP—BNB—ADA—DOGE—TRX—LINK—AVAX—DOT—LTC—
Live

What is the mempool? Bitcoin's waiting room and fees explained

The mempool is the waiting room where Bitcoin transactions sit before they confirm. This guide explains what it is, why every node keeps its own, how fees decide who gets confirmed first, and how to avoid overpaying.

By Himanshu Sakre

Published · 6 min read

The mempool is Bitcoin's waiting room. It is the holding area where a transaction sits after you send it and before a miner packs it into a block. Every node on the network keeps its own copy. When a payment shows as unconfirmed, that is where it lives, waiting its turn.

Mempool is short for memory pool. Each full node stores pending transactions it has checked and judged valid, then passes them to its neighbors. Bitcoin's explorer mempool.space calls it the queue of pending, unconfirmed transactions held by a network node. Nothing in it has settled yet. It is a queue, not a ledger.

What the mempool actually does

Think of a busy post office with one clerk. People keep arriving with letters, but the clerk can only handle a batch at a time. Everyone else waits. Bitcoin works the same way. Transactions pour in all day, and a new block arrives only about every ten minutes, so the overflow has to wait somewhere. That somewhere is the mempool.

Room in each block is capped. A Bitcoin block holds about four million weight units, which works out to a few thousand transactions at most, whatever the demand that day. Miners cannot just make blocks bigger to clear a backlog. So when more people want to transact than a block can fit, the mempool is where the line forms, and the fee becomes the tiebreaker.

Why there is no single mempool

Here is the part that surprises people. No one master mempool is shared by everyone. Each node keeps its own, built from the transactions it has seen and the rules it runs. Views differ. River, a bitcoin company, puts it bluntly: there is no single mempool and few if any nodes keep the entire mempool. Your wallet's view is really one node's best guess.

Transactions spread by gossip. Your wallet hands the transaction to a few nodes, each of those tells a few more, and within seconds most of the network has seen it. That spread is fast but not instant, and any node will reject anything that breaks its rules or pays below its floor. A transaction one node accepts, another may never hold.

This matters more than it sounds. Two explorers can show different pending counts at the same moment, because they are watching different nodes. Neither is wrong. They just see slightly different slices of the network at that second.

How your transaction gets picked

Miners, the people and firms who do the work of building blocks, pick transactions from the mempool by fee rate, not by the total fee you attach or the amount you are sending. mempool.space says Bitcoin Core selects transactions in descending order of fee rate, measured in satoshis per virtual byte, or sat/vB. Pay a higher rate and you move up the queue. Pay a low one and you wait.

Size here means data size, not dollar value. A transaction built from many small unspent coin pieces, or UTXOs, is bulky, so it costs more to confirm than a lean one carrying the same fee. You can send a fortune and still wait behind a tiny payment that paid more per byte. That is why the fee rate is the number that matters.

A quick example shows why. Say the network is busy and the going rate for the next block is 20 sat/vB. A simple transaction of about 140 virtual bytes would need roughly 2,800 satoshis to get in fast, a fraction of a dollar at most prices. A bulkier transaction of 400 virtual bytes, in the same hurry, would need closer to 8,000 satoshis. Same speed, bigger bill, purely because of size.

What happens when the mempool fills up

Every mempool has a ceiling. By default, mempool.space notes, Bitcoin Core allocates 300MB of memory for its mempool. Once a node reaches that limit, it starts dropping the lowest-paying transactions to make room for better-paying ones. In calm periods the mempool can empty out, and even a one sat/vB transaction confirms within a few blocks. In a rush it backs up, fees climb, and cheap transactions can sit for hours.

Transactions do not wait forever. If one stays stuck for about two weeks, 336 hours by default in Bitcoin Core, a node drops it from its mempool and the coins never left your wallet. You can then try again with a higher fee. There is no central undo button on the network, so this timeout is the cleanup.

Confirmed, unconfirmed and how final a payment is

Leaving the mempool is the goal. One block in, and your transaction has a single confirmation. It is no longer pending. Each block mined on top adds another confirmation and makes any reversal harder. Many exchanges wait for a handful, often around six, before they treat a deposit as settled.

Until that first confirmation, a payment is not final. A transaction still sitting in the mempool can be replaced or dropped, which is why treating an unconfirmed transfer as done is risky for anything that matters. Wait for the block. For small, everyday sums the wait is usually minutes. For a house-sized transfer, patience is cheap insurance.

How to read fees before you send

You do not have to guess. Fee estimators, including the one on mempool.space, read the current mempool and suggest a sat/vB rate for fast, medium or slow confirmation. Low rate, long wait. A good wallet does this for you and shows the trade-off, so you can decide how much speed is worth before you sign. On a phone wallet it is often one tap, and on node software you can set the rate by hand.

If you underpay and get stuck, you are not always trapped. Two tools can help. Replace-by-fee lets you resend the same transaction with a higher fee, if your wallet flagged it as replaceable. Child-pays-for-parent lets a new, higher-fee transaction drag a stuck one along behind it. Both are standard, and most modern wallets support at least one.

What to watch

Watch the fee market, not the price, when you are timing a payment. Fees swing with demand, and demand spikes when something new floods the chain with data. During the Ordinals wave of December 2023, fee rates ran into the hundreds of sat/vB, many times the usual handful. If you are not in a hurry, sending during a quiet stretch can cost a fraction of that.

A full mempool is not a crisis. It is the fee market doing its job, rationing the limited room in each block to whoever values it most that hour. Nobody can promise a confirmation time. A backlog can clear in one block if luck and hash rate line up, or linger if blocks come slowly. Read the mempool as a weather report, not a timetable.

Frequently asked

What is the mempool in simple terms?

The mempool is Bitcoin's waiting area for transactions. After you send a payment, it sits in the mempool until a miner includes it in a block and it becomes confirmed. Every node keeps its own mempool, so a transaction is pending there, not lost, until it either confirms or times out.

How long does a transaction stay in the mempool?

It depends on the fee you paid and how busy the network is. A high fee rate can confirm in the next block or two. A low one may wait hours during congestion. If a transaction stays unconfirmed for about two weeks, a node drops it and the coins remain in your wallet.

Can I speed up a stuck transaction?

Often, yes. If your wallet marked the transaction as replaceable, replace-by-fee lets you resend it with a higher fee. Child-pays-for-parent is another option, where a new high-fee transaction pulls the stuck one through. Both are widely supported, though you cannot cancel a transaction once it confirms.

Sources, and what is behind them

  1. Mempool FAQ, mempool.spaceDocumentation
  2. Mempool, RiverDocumentation