A transaction mempool is a Bitcoin node’s local collection of transactions it has accepted but that are not yet confirmed in a block. Mempool is short for “memory pool,” referring to this temporary storage of pending transactions. There is no single authoritative, network-wide Bitcoin mempool: each node maintains its own view of pending activity.
How Transactions Enter a Mempool
A signed transaction is broadcast to connected nodes. Each receiving node checks transaction validity, including signatures and spending conditions, and applies its own admission policies. If accepted, the node may store the transaction and relay it to peers. Broadcasting therefore means distributing a transaction, not recording it on the blockchain.
Each node’s transaction mempool reflects the transactions it has received and accepted. Different connections, arrival times and policies can produce different pending sets, so a transaction visible to one node may be absent from another. A block explorer’s pending view reflects its data sources rather than a definitive network-wide queue. Broadcast, local acceptance and block inclusion describe a common route, not a mandatory shared waiting stage; transactions can also reach miners through other paths.
How Fees Affect Block Selection
A transaction mempool is not a first-in, first-out queue. Miners select transactions for candidate blocks, generally seeking to earn fees within Bitcoin’s limited block capacity. Fee rate—the fee relative to a transaction’s virtual size, commonly expressed in satoshis per virtual byte—usually matters more than the total fee alone. Transaction dependencies and miners’ selection policies can also affect inclusion.
In a hypothetical example, a transaction paying 2,000 satoshis for 200 virtual bytes has a fee rate of 10 satoshis per virtual byte. Another paying 3,000 satoshis for 600 virtual bytes offers only 5, despite its larger total fee. When demand exceeds available block capacity, transactions compete for inclusion and less competitive fee rates may mean longer waits. A competitive fee rate can improve inclusion prospects, but neither admission nor a higher fee guarantees confirmation, next-block inclusion or a particular waiting time. Fee comparisons describe incentives rather than promised processing speeds.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedConfirmation and Block Validation
A transaction receives its first confirmation when it is included in a valid block on the accepted chain. Full nodes independently validate that block against Bitcoin’s consensus rules, including whether its transactions spend funds validly. They do not treat a miner’s selection as sufficient proof of validity. Once nodes accept the block, they remove its confirmed transactions from their pools.
Admission to a transaction mempool is not a prerequisite for block inclusion. A node can receive and validate a block containing transactions it never previously stored. Local acceptance is therefore a pending status, not guaranteed settlement or a substitute for consensus validation. Further blocks added after the containing block increase the transaction’s confirmation count.
Why Unconfirmed Transactions Leave a Pool
A transaction mempool can also lose unconfirmed entries through eviction, expiry or replacement. A node may evict transactions when its configured memory limit is reached, often removing less competitive fee-rate entries. It may expire transactions after a locally determined retention period or accept a conflicting replacement under its replacement policy. Capacity and retention settings are local choices, not a universal mempool-size limit imposed by Bitcoin’s consensus rules.
Removal from one node does not cancel a transaction across the network. Other nodes may still retain it, and it may be broadcast again or reach a miner later. Its eventual inclusion depends on whether it remains valid and is selected for a block. Absence from one pending view therefore proves neither confirmation nor permanent rejection.
Interpreting a Pending Status
When a wallet reports a transaction as pending, distinguish the wallet’s own submission status from a node’s acceptance and from actual block inclusion. A fee estimate describes current conditions and policy assumptions, not a reservation of space in a future block. Changing demand can make an earlier estimate less competitive.
Some wallets support fee-adjustment mechanisms under the applicable transaction and node policies, but a user should check what the wallet is actually constructing and which outputs it spends. Merely seeing an entry disappear from an explorer does not establish that the funds are available for an unrelated new payment. Checking the transaction and relevant spend status on the correct network helps avoid treating an incomplete view as a final outcome.