What Is a Bitcoin Mempool? How It Works and Why It Matters

A mempool, short for memory pool, is a temporary holding area maintained by a blockchain node for transactions that have been received but have not yet been included in a confirmed block.

In Bitcoin, the mempool plays an important role between transaction creation and blockchain confirmation. When you send BTC, your transaction is broadcast to the Bitcoin network. Nodes validate it according to their rules and may keep it in their local mempool while it waits for a miner to include it in a block.

Understanding the Bitcoin mempool can help explain why transactions sometimes remain unconfirmed, why transaction fees change, why higher-fee transactions can receive priority, and why different Bitcoin mempool websites can show different numbers of pending transactions.

If you are new to Bitcoin and blockchain technology, start with our guide to what blockchain is and how blockchain technology works.

What Is a Mempool?

A mempool is a collection of unconfirmed transactions maintained by an individual blockchain node.

It is important to understand that there is not one single global Bitcoin mempool. Each node maintains its own mempool, and the contents can differ depending on which transactions the node has received, its validation rules, local policy settings, and available capacity.

Bitcoin Core describes its mempool as storing transactions that are valid according to the node’s current best chain and may be included in a future block. Not every transaction seen by a node is necessarily accepted into its mempool.

You can think of the mempool as a waiting area between the Bitcoin network and the blockchain:

Transaction created → Broadcast → Node validation → Mempool → Block → Blockchain confirmation

How Does the Bitcoin Mempool Work?

The process can be divided into several stages.

1. A User Creates a Bitcoin Transaction

Suppose Bob wants to send 1 BTC to Alice.

Bob’s wallet creates a transaction that specifies which Bitcoin outputs are being spent, where the new outputs should go, and the transaction fee. The transaction is digitally signed using the appropriate private key.

The wallet then broadcasts the transaction to Bitcoin nodes.

2. Nodes Receive the Transaction

When a Bitcoin node receives a transaction, it does not automatically accept it into its mempool.

The node performs a series of checks to determine whether the transaction is acceptable under Bitcoin’s consensus rules and the node’s local relay and mempool policies.

Bitcoin Core, for example, can reject transactions that do not meet minimum fee requirements, conflict with transactions already in the mempool without satisfying replacement rules, or fail other policy requirements.

3. The Transaction Enters the Mempool

If the transaction passes the relevant checks, the node can add it to its local mempool.

The node can then relay the transaction to other peers. Those peers independently validate it and may add it to their own mempools.

Because transactions propagate through a peer-to-peer network, different nodes can temporarily have different mempool contents.

4. Miners Select Transactions

Bitcoin miners construct candidate blocks using transactions available to them.

Transaction fees are an important consideration when selecting transactions because miners generally seek to maximize the fees earned from the available block space.

However, transaction selection is not simply a universal first-in-first-out queue. Transaction dependencies, fee rates, policy rules, and block-space constraints can all affect which transactions are selected.

Bitcoin Core’s current block-building and fee-estimation systems explicitly account for transaction relationships and fee rates when constructing blocks.

5. The Transaction Is Included in a Block

Once a miner includes the transaction in a valid block and that block is accepted by the network, the transaction is no longer an unconfirmed mempool transaction for that node.

The transaction is now part of the blockchain.

As additional blocks are built on top of that block, users generally refer to the transaction as having additional confirmations.

Bitcoin Mempool vs Blockchain

The distinction is important: being in the mempool does not mean a transaction has been confirmed.

Why Does the Bitcoin Mempool Matter?

The mempool matters because it provides a window into the demand for Bitcoin block space and helps connect transaction broadcasting with block production.

1. Transaction Confirmation Times

When the number of transactions waiting for block inclusion increases, users may have to wait longer for a transaction to be included at a particular fee rate.

During periods of high demand, transactions paying relatively low fee rates may remain unconfirmed while higher-fee transactions are selected for available block space.

2. Transaction Fees

The mempool is closely connected to Bitcoin’s transaction fee market.

Users compete for limited block space by attaching fees to their transactions. The relevant metric is generally the fee rate, commonly expressed in satoshis per virtual byte (sat/vB), rather than simply the total BTC fee. Bitcoin Core represents fee rates in satoshis per virtual byte.

When demand for block space is high, users who want faster confirmation may choose a higher fee rate.

3. Network Congestion

A growing mempool can indicate that transactions are arriving faster than they are being included in blocks.

During congestion, users may experience:

• Longer confirmation times
• Higher recommended fee rates
• More competition for block space
• Greater variation between low- and high-fee transactions

However, mempool size alone should not be treated as a perfect measure of congestion. Different nodes can have different mempool contents, and transaction sizes and fee rates also matter.

Why Do Higher-Fee Transactions Often Get Confirmed Faster?

Bitcoin blocks have limited capacity, so miners cannot include every waiting transaction in every block.

When there is more demand than available block space, miners have an economic incentive to consider transactions that offer higher fee revenue relative to the amount of block space they consume.

This is why wallets often recommend a higher fee rate when the network is busy.

Bitcoin Core also maintains fee-estimation functionality that uses recent mempool and mined-block information to estimate fee rates for transaction inclusion.

What Is Mempool Congestion?

Mempool congestion occurs when a large number of transactions are waiting to be confirmed and the available block space cannot accommodate all of them immediately.

For example, imagine that many users suddenly want to move Bitcoin at the same time. New transactions enter nodes’ mempools, but miners can only include a limited amount of transaction data in each block.

If demand remains high, lower-fee transactions may have to wait for future blocks.

Once demand falls or more transactions are confirmed, the backlog can decrease.

What Happens to Low-Fee Transactions?

A low-fee transaction does not necessarily become permanently invalid simply because it is not confirmed quickly.

However, a transaction can eventually disappear from a particular node’s mempool due to local policies such as expiration or size limits.

Bitcoin Core’s mempool implementation supports expiration and size-based eviction. Transactions can therefore leave a node’s mempool without being included in a block.

This does not necessarily mean that the transaction has been permanently erased from the entire Bitcoin network. Another node may still have it, or the wallet may be able to rebroadcast it.

Why Can a Bitcoin Transaction Disappear From the Mempool?

There are several possible reasons.

• The transaction was included in a block.
• The transaction expired from a node’s mempool.
• The node’s mempool reached its size limit and transactions were evicted.
• The transaction was replaced under applicable replacement rules.
• A blockchain reorganization changed the transaction’s status.
• The node restarted without retaining or restoring that transaction.
• The transaction was not accepted by that particular node in the first place.

Bitcoin Core documentation specifically identifies expiration, size limiting, and reorganizations among reasons transactions can be removed from the mempool.

What Is Replace-by-Fee (RBF)?

Replace-by-Fee (RBF) is a mechanism that can allow an unconfirmed transaction to be replaced with another transaction that spends the same inputs under the applicable replacement rules and pays a higher fee rate or otherwise satisfies the required conditions.

RBF can be useful when a user originally selected a fee that is too low and wants to increase the transaction’s chances of confirmation.

For example:

1. Bob broadcasts a Bitcoin transaction with a relatively low fee rate.
2. The transaction remains unconfirmed while network demand increases.
3. Bob creates a replacement transaction with a higher fee.
4. If the replacement satisfies the network’s applicable replacement rules, nodes may accept the replacement instead.

This is one reason the mempool should not be viewed as a simple permanent queue.

Transaction Dependencies in the Mempool

Bitcoin transactions can depend on other unconfirmed transactions.

For example, transaction B might spend an output created by transaction A. Until transaction A is confirmed, transaction B may depend on it.

Bitcoin Core tracks relationships between transactions in the mempool, including parent and child transactions. Its current transaction-graph system uses these relationships when handling transaction selection and mempool management.

This becomes particularly important for advanced fee-management techniques such as Child Pays for Parent (CPFP).

What Is Child Pays for Parent (CPFP)?

Child Pays for Parent is a technique in which a later transaction pays a sufficiently high fee to encourage miners to include both it and an earlier dependent transaction.

For example, if a parent transaction has a relatively low fee, a child transaction spending one of its outputs can offer a higher fee. The combined package can then become attractive for block inclusion.

This demonstrates why transaction fee analysis can involve groups of related transactions rather than looking at every transaction in isolation.

Does Every Bitcoin Node Have the Same Mempool?

No.

This is one of the most important things to understand about Bitcoin’s mempool.

Each node maintains its own local mempool. Two nodes may therefore show different pending transactions at the same moment.

Differences can occur because:

• One node received a transaction before another.
• Transactions have not propagated everywhere yet.
• Nodes use different configuration or policy settings.
• A transaction was accepted by one node but rejected by another.
• One node has already removed a transaction from its mempool.

Therefore, public mempool explorers should be understood as views of network activity rather than a single authoritative global queue.

Does the Mempool Prevent Double Spending?

The original version of this article described the mempool as preventing double-spending attacks. That is too broad.

The mempool is involved in validating and managing unconfirmed transactions, including transactions that conflict with transactions already known to a node. Bitcoin Core maintains information about transactions spending the same inputs and applies replacement and validation policies.

However, the mempool itself does not provide final protection against double spending. Bitcoin’s broader consensus system, transaction validation, Proof of Work, block confirmations, and the decentralized network all play roles in determining which transactions become part of the accepted blockchain.

For a broader look at Bitcoin and blockchain security, read our article about blockchain security risks.

What Happens When a Transaction Is Confirmed?

When a miner includes a valid transaction in a block and the network accepts that block, the transaction moves from an unconfirmed state toward confirmed status.

The transaction is no longer simply waiting in the mempool. It is now part of a block in the blockchain.

As subsequent blocks are added, the transaction gains additional confirmations.

For a deeper understanding of how miners process transactions and add blocks, see our guide to Bitcoin mining.

How the Mempool Relates to Bitcoin Mining

The mempool and Bitcoin mining are closely connected.

The mempool contains transactions that may be available for inclusion in future blocks, while miners construct candidate blocks using transactions available to them.

Miners then compete to find a valid Proof of Work solution for their candidate blocks.

Hash functions are fundamental to this process. To understand the cryptographic technology behind Bitcoin mining and Proof of Work, read Hash Functions in Blockchain: How They Work.

Mempool and Bitcoin Fees

Bitcoin transaction fees are generally determined by the fee attached to a transaction and the transaction’s size or virtual size.

A useful way to think about the fee market is:

More demand for block space → greater competition → higher fee rates may be required for faster confirmation.

When demand decreases, lower fee rates may become sufficient for relatively quick inclusion.

This dynamic is why checking current network conditions can be useful before sending a Bitcoin transaction.

How Wallets Use Mempool Information

Bitcoin wallets can use information about recent blocks and pending transactions to estimate an appropriate fee rate.

A wallet may present several options such as:

• Economical fee
• Normal fee
• Priority fee

The exact options depend on the wallet.

Fee estimation is not a guarantee of confirmation time because network conditions can change after the transaction is broadcast.

Bitcoin Mempool vs Ethereum Mempool

The term mempool is also commonly used when discussing Ethereum and other blockchain networks, but the exact mechanics differ between networks.

Bitcoin uses Proof of Work and miners select transactions for blocks. Ethereum uses Proof of Stake and validators propose blocks.

The general concept is similar: transactions that have not yet been included in a block may be held and propagated by network participants. However, transaction structures, fee mechanisms, execution models, and transaction-selection policies differ between blockchains.

Therefore, the Bitcoin mempool should not automatically be assumed to work exactly like an Ethereum transaction pool.

A Simple Example of a Bitcoin Mempool

Imagine that Bob wants to send 1 BTC to Alice.

1. Bob creates and signs the transaction.
2. Bob’s wallet broadcasts the transaction.
3. Bitcoin nodes receive the transaction.
4. Nodes independently validate it.
5. Eligible nodes add it to their local mempools.
6. The transaction is relayed to other peers.
7. A miner selects the transaction for a candidate block.
8. The miner finds a valid Proof of Work solution.
9. The block is broadcast and validated by other nodes.
10. Bob’s transaction becomes part of the blockchain.
11. Additional blocks provide additional confirmations.

This entire process connects Bitcoin’s transaction layer with its decentralized consensus system.

Why Bitcoin Mempool Data Is Useful

Mempool information can provide useful insight into current network conditions.

Users can examine mempool activity to understand:

• How many transactions are waiting for confirmation
• Which fee-rate ranges are active
• Whether demand for block space is increasing
• Whether lower-fee transactions may take longer to confirm
• How transaction fees are changing

Developers and node operators can also use mempool information for network monitoring, fee estimation, transaction testing, and troubleshooting.

Common Misconceptions About Bitcoin Mempools

There Is One Global Bitcoin Mempool

Not exactly. Each node maintains its own mempool. Different nodes can have different transaction sets.

Every Transaction Must Enter Every Mempool

No. Nodes independently decide whether to accept and relay transactions according to their validation and policy rules.

A Transaction in the Mempool Is Confirmed

No. A mempool transaction is still unconfirmed. Confirmation occurs when the transaction is included in a valid block.

The Highest-Fee Transaction Is Always Confirmed First

Not necessarily. Transaction selection can involve fee rates, transaction size, dependencies, package relationships, and other block-building considerations.

If a Transaction Leaves a Mempool, It Has Been Deleted From Bitcoin

Not necessarily. A transaction can leave one node’s mempool because of expiration, size limits, replacement, reorganization, or other local conditions.

Frequently Asked Questions About Bitcoin Mempools

What is a Bitcoin mempool?

A Bitcoin mempool is a local pool of unconfirmed transactions maintained by a Bitcoin node. Transactions may remain there until they are included in a block, replaced, expired, or removed for another reason.

Is the Bitcoin mempool the same for every node?

No. Each node maintains its own mempool, and the contents can differ because of transaction propagation, local policy settings, capacity limits, and timing.

How long does a Bitcoin transaction stay in the mempool?

There is no single universal time. A transaction may be confirmed quickly, remain pending for an extended period, be replaced, or eventually be removed from a particular node’s mempool according to that node’s policies.

Why is my Bitcoin transaction stuck in the mempool?

A transaction may remain unconfirmed because its fee rate is relatively low compared with current demand for block space. Other factors can also affect confirmation, including transaction dependencies and changes in network conditions.

Can I increase the fee of an unconfirmed Bitcoin transaction?

In some circumstances, yes. Replace-by-Fee (RBF) can allow a compatible unconfirmed transaction to be replaced with a higher-fee transaction under the applicable rules.

What happens when a Bitcoin transaction leaves the mempool?

If it is included in a block, it becomes part of the blockchain. If it is removed for another reason, it may remain unconfirmed and could potentially be rebroadcast or otherwise handled depending on the circumstances.

Does a larger mempool mean Bitcoin is broken?

No. A larger mempool generally means that more transactions are waiting for available block space, although mempool size alone does not provide a complete picture of network conditions.

What is the difference between a mempool and a blockchain?

The mempool contains unconfirmed transactions that a node may consider for future block inclusion. The blockchain contains blocks that have been accepted as part of the network’s current chain.

Conclusion

The Bitcoin mempool is an important part of the journey from an unconfirmed transaction to a confirmed blockchain transaction.

When a Bitcoin transaction is broadcast, nodes independently validate it and may store it in their local mempools. Miners can then select transactions from available mempool data when constructing candidate blocks. Once a transaction is included in a valid block, it becomes part of the blockchain.

The mempool also helps explain Bitcoin’s transaction-fee market. When demand for block space increases, users may compete through higher fee rates for faster confirmation. When demand falls, lower fee rates may become sufficient.

Most importantly, remember that there is no single global Bitcoin mempool. Mempools are local to nodes and can change constantly as transactions are received, confirmed, replaced, expired, or evicted.

Understanding mempools therefore gives you a better understanding of Bitcoin transactions, transaction fees, mining, confirmation times, and the way the Bitcoin network processes activity without relying on a central transaction-processing authority.