The mempool (memory pool) is the set of valid transactions that a Bitcoin node has accepted but that are not yet in a block, which is what unconfirmed means. Each node keeps its own mempool. A transaction waits there until a miner includes it in a block or it leaves the pool in another way.
Unconfirmed transactions are transactions that are still waiting for confirmation. A transaction is confirmed once a miner, which is a person or company that adds blocks to the blockchain, includes it in a block. A block is a batch of transactions, and the blockchain is the shared record of all the blocks.
A Bitcoin node is a computer that connects to the Bitcoin network. Nodes check the transactions and blocks they receive and pass them on to other nodes.
How Does a Transaction Reach the Bitcoin Mempool?
A Bitcoin transaction reaches a node’s mempool in four steps, and the third one is the step that puts it there.
- Create and sign. A wallet builds the transaction, which names the unspent outputs it spends and the new outputs it creates, and signs it with the sender’s private key, a secret that only the sender is meant to hold and that makes it possible to spend the BTC. An unspent output is a piece of BTC that an earlier transaction sent to the sender and that has not been used yet.
- Broadcast. The wallet broadcasts the transaction to the network through a node. That node passes it to the other nodes it is connected to, which are called its peers.
- Wait in mempools. Each node that keeps a mempool and finds the transaction valid under its own rules and policy adds it to its mempool and can pass it on to its own peers.
- Confirmed in a block. A miner includes the transaction in a block. The transaction is then confirmed and no longer waits in the mempool.
Before a Bitcoin node accepts a transaction into its mempool, it checks that the transaction is valid. The inputs must be unspent outputs, the outputs must not add up to more than the inputs, and each input must satisfy the spending condition of the output it uses. The node also applies its own relay policy, a set of extra rules that are local to that node.
Is There One Mempool for the Whole Bitcoin Network?
The phrase “the mempool” is shorthand for many separate pools, one per node, and no single pool belongs to the whole Bitcoin network. Each node builds its own mempool from the transactions that this node has accepted.
Two nodes can hold different mempools at the same moment. A transaction can take time to pass from peer to peer, so a node that it has not reached yet does not hold it. Each node also applies its own policy and its own size limit, so a node can refuse or drop a transaction that another node keeps.
The mempool lives in a node’s memory, which is where the name memory pool comes from. It is separate from the blockchain. The blockchain records the transactions that are already in blocks, while a node’s mempool holds only the transactions that are still waiting.
What Is the Difference between Consensus Rules and Mempool Policy?
Consensus rules are the rules that decide whether a transaction or a block is valid for the whole Bitcoin network. Mempool policy, also called relay policy, is a set of additional rules that one node applies to decide which unconfirmed transactions it accepts into its mempool and passes on. Policy covers unconfirmed transactions and does not apply to transactions that are already in blocks.
A Bitcoin transaction can be valid under the consensus rules and still be refused by a node’s mempool policy. Dust is one example. Dust is an output so small that spending it would cost more in fees than it is worth. As of October 2026, Bitcoin Core, which is node software, generally does not accept or relay transactions with such outputs by default, although the consensus rules do not forbid dust.
Mempool policy is local and configurable, so the person who runs a node can change its settings. A miner can also include a transaction that a node’s policy would refuse, as long as the consensus rules allow it.
How Do Miners Choose Which Transactions Go into a Block?
A block template is the list of transactions proposed for the next block. In pool mining, the mining pool builds the block template from the transactions in a node’s mempool, and a miner who builds blocks alone does it themselves. The template typically fills the available space starting with the highest fee rates.
A fee is the difference between the total value of a transaction’s inputs and the total value of its outputs, and it goes to the miner who includes the transaction in a block. A fee rate is the fee divided by the transaction’s size in virtual bytes (vbytes), written in satoshis per vbyte (sat/vB).
A satoshi is one hundred millionth of a BTC. A vbyte is the unit Bitcoin uses to measure a transaction’s size for fees. It is defined through weight units, the unit in which Bitcoin measures how much room a transaction takes in a block, and one vbyte equals four weight units.
Block space is limited, so a block cannot hold every waiting transaction. The consensus limit for a block is 4 million weight units, which equals 1 million vbytes. The example below uses a made-up block with room for only 450 vbytes, so the effect is easy to see. Every number in it is made up, not real, and not a fee recommendation.
| Transaction (made up) | Size (vbytes) | Fee rate (sat/vB, made up) | Total fee (satoshis, made up) | Fits in the 450-vbyte block? |
|---|---|---|---|---|
| A | 200 | 30 | 6,000 | Yes, taken first |
| B | 250 | 20 | 5,000 | Yes, taken second |
| C | 400 | 16 | 6,400 | No |
Transaction C pays the largest total fee, 6,400 satoshis, but has the lowest fee rate, so it comes last and finds no room. If C were taken first, it would use 400 of the 450 vbytes, and neither A at 200 vbytes nor B at 250 vbytes would fit in the remaining 50. The block would then bring 6,400 satoshis instead of the 11,000 satoshis that A and B bring together, which is why, in this example, the order follows the fee rate rather than the total fee.
Real nodes and miners apply further rules. As of October 2026, for example, Bitcoin Core considers a parent transaction and a child transaction that depends on it together when it orders transactions, instead of looking at each one alone.
A transaction can wait in the mempool when its fee rate is low compared with the other waiting transactions, or when blocks fill up with transactions that have higher fee rates. A node whose policy refuses a transaction does not hold it at all, and other nodes can still hold it.
How Does a Transaction Leave the Mempool?
A transaction can leave a node’s mempool in several ways, and confirmation is only one of them.
- Confirmed. A block that includes the transaction is added to the blockchain, so the transaction is confirmed and the node no longer holds it as waiting.
- Replaced. As of October 2026, replace-by-fee (RBF) is a node policy under which a sender can replace an unconfirmed transaction with a version that pays a higher fee, and nodes can accept the replacement. A node that accepts the replacement removes the original transaction from its mempool.
- Conflicted. Two transactions conflict when they spend the same output. If one of them is confirmed, the other can no longer be valid, and a node removes it.
- Expired. A node removes a transaction that has waited longer than a time limit set by that node.
- Evicted. Mempool size is the amount of data a node’s mempool holds, and the node sets its limit. When the mempool reaches that limit, the node drops the transactions with the lowest fee rate first, which is called eviction.
A transaction that leaves a node’s mempool without being confirmed has not been reversed. The node’s mempool simply no longer holds it. The outputs the transaction was spending are not spent on the blockchain until a block confirms a spend, so a dropped transaction can leave the sender’s BTC where it was. A transaction that one node has dropped can still be held by another node, because nodes can hold different mempools.
What Does a Transaction in the Mempool Not Tell You?
A transaction in the mempool is not confirmed. Unconfirmed transactions, also called pending transactions, can still be replaced or dropped, so they are not final. Bitcoin transactions are designed to become irreversible as more blocks follow the block that confirms them, and each block added on top makes a reversal harder. A transaction that is only waiting in a mempool has not reached that stage.
A transaction that appears in a mempool is not in the blockchain yet, and seeing it there says nothing certain about whether it has reached other nodes. The mempool also makes no promise that a transaction will confirm, or when. A transaction that a wallet shows as pending can be one that is still waiting in one or more mempools. What the mempool does tell you is that a node has found the transaction valid under its own rules and is holding it while it waits for a block.
November 18, 2026











