Every Bitcoin transaction spends time in a waiting room before it is confirmed. That waiting room is the mempool, and understanding it is the difference between overpaying on every transaction and knowing roughly what a confirmation should cost. It is also one of the few onchain datasets that is genuinely real time.
What the mempool actually is
There is no single mempool. Each node on the network keeps its own list of valid transactions it has heard about and not yet seen in a block. These lists are similar but not identical, because transactions propagate at different speeds and nodes apply slightly different acceptance rules and size limits. When a site like mempool.space shows you the mempool, it is showing you one node’s view, which is close enough to the network’s for practical purposes.
A transaction stays there until a miner includes it in a block, it is replaced, or the node drops it for sitting too long. Nothing about being in the mempool guarantees confirmation.
Why miners sort by fee rate, not fee
Block space is capped, so miners fill blocks with whatever earns the most per unit of space. The relevant number is therefore the fee rate, measured in satoshis per virtual byte, rather than the total fee. A large transaction paying a high total fee can be outbid by a small one paying less in absolute terms, because the small one buys less space for the same revenue.
This has a practical consequence. Transaction size depends on how many inputs you are spending. A wallet consolidating many small inputs builds a physically larger transaction and pays more to reach the same confirmation speed. This is the same mechanism explained from the coin side in What Is a UTXO.
Reading the fee bands
Mempool explorers group pending transactions into fee-rate bands and show how many blocks of demand sit at each level. That visualisation answers the only question that matters when you are about to send: how far down the queue does a given fee rate place you. If there are three blocks of transactions paying more than your rate, you are waiting at least three blocks, which is roughly thirty minutes on average but highly variable.
The backlog empties and refills on a daily and weekly rhythm. Weekend fee rates are usually lower. Sustained congestion generally traces to a specific cause, whether an inscription wave, an exchange consolidating, or a period of genuine transactional demand. Bitcoin Transaction Fees and the Fee Market covers the economics in more depth.
What to do when a transaction is stuck
Two mechanisms exist. Replace-by-fee lets you resend the same transaction with a higher fee, if the original was flagged as replaceable when you sent it. Child-pays-for-parent works from the receiving side: you spend the unconfirmed output in a new high-fee transaction, and miners must include the parent to collect on the child. Most modern wallets expose one or both. The practical guide is in Transaction Stuck.
Why this matters beyond fees
Mempool depth is a demand signal that arrives before the block data does. A sustained backlog means people are willing to pay to transact now, which is information about urgency that confirmed-transaction metrics only reveal later. It also feeds miner revenue, which matters for the security budget as block subsidies shrink. That link runs through miner behaviour and eventually into supply.
Common questions
Can a transaction be stuck forever? It can be dropped from mempools after a timeout, typically around two weeks, at which point the coins were never spent and are simply still yours. It cannot be partially sent.
Is an empty mempool bad for Bitcoin? It is neutral in the short run and a real question in the long run, because fees eventually have to replace the block subsidy. One quiet week means nothing.
Why do fee estimates differ between wallets? Each wallet uses its own algorithm and its own node’s view, and they target different confirmation times. Checking a mempool explorer directly before a large send is worth the thirty seconds.
Research and education only, not financial advice.
Leave a Reply