
A mempool is a specialized digital space—think of it as a "waiting room" for cryptocurrency transactions. Every blockchain node (network participant) maintains its own mempool, temporarily storing transactions that users have initiated but have not yet been processed and added to the blockchain.
The word "mempool" is formed from "memory" and "pool." This name captures its purpose: a shared memory pool where transactions line up, waiting to be included in the blockchain.
Notably, the mempool concept was first implemented in the Bitcoin network by Satoshi Nakamoto, the creator of Bitcoin. Bitcoin not only popularized blockchain technology but also introduced this efficient transaction-handling mechanism. Since then, other blockchain projects—including Ethereum and numerous other cryptocurrency networks—have adopted and adapted the mempool concept.
It's important to recognize that mempools exist in every blockchain system, though some projects use different terminology. For example, the Parity blockchain project calls the mempool a "Transaction Queue," which serves the same core function.
Every transaction in a mempool takes up a certain amount of data. Typically, a single transaction is just a few kilobytes (KB). The mempool size is the sum of the kilobytes of all transactions currently queued for processing.
A large mempool is a key indicator of network conditions. It shows there are many transactions awaiting confirmation, which could be caused by increased user activity, market events, or network limitations.
Mempool size charts for Bitcoin reveal a clear pattern: the mempool often swells during periods of high price movement—both upswings and downturns. That’s because volatility prompts more users to buy, sell, or transfer funds.
Technically, each node can set its own mempool size limit. If the mempool exceeds this threshold, the system may automatically impose a minimum transaction fee. This helps regulate network load and ensures transactions with higher fees get priority processing.
Mempools play a critical role in how blockchain nodes operate. Understanding this role means examining how transactions are written to the blockchain.
For a transaction to be permanently added to the blockchain, it must go through several steps. First, it needs to be included in a block—the blockchain’s basic unit. However, not every node can create new blocks.
In Proof-of-Work blockchain systems—such as Bitcoin—only miners can add transactions to blocks. Miners use computational power to solve complex mathematical problems, and those who succeed gain the right to create a new block.
In Proof-of-Stake systems—like modern Ethereum—validators add transactions to blocks. Validators are chosen based on how much cryptocurrency they've staked as collateral.
After a user creates a transaction, they can’t see it on the blockchain immediately. They must wait for a validator or miner to verify the transaction, approve it for inclusion, and then write the block to the blockchain. During this entire waiting period—from creation to final recording—the transaction sits in the mempool. The mempool acts as a buffer between the user and the blockchain, keeping transaction processing orderly.
To fully understand the mempool, note that a blockchain can have many mempools: each node keeps its own transaction pool for pending transactions. These individual mempools, distributed across all network nodes, together form the collective mempool for the blockchain.
Here’s how the mempool process works: When a user creates a transaction in their wallet, it’s sent to the nearest available node. That node immediately adds the transaction to its local mempool and places it in line for validation.
Validation checks that all transaction data is correct. The node ensures the sender has enough funds, the addresses are accurate, the transaction format matches protocol requirements, and no network rules are violated.
Once a transaction passes validation, its status becomes "pending." Only pending transactions can be selected by miners or validators for inclusion in new blocks. These participants scan the mempool and choose which transactions to add to the next block.
After a miner or validator creates a new block and attaches it to the blockchain, information about the block and its transactions is broadcast to the entire network. All nodes receive this notification and safely remove those transactions from their local mempools, since they are now permanently recorded. This is how mempools stay synchronized and data remains consistent across the blockchain.
To illustrate the mempool’s function and the full lifecycle of a cryptocurrency transaction, let’s look at a practical example: sending 0.01 BTC to a friend.
Transaction Initiation. First, you get your friend’s crypto wallet address—a unique character string you’ll use as the recipient address. In your wallet interface, enter the recipient’s address, the amount to send, and accept the suggested transaction fee. After checking all the details, click "send."
Entering the Mempool. Right after you send it, your transaction is added to the mempool of the nearest node and marked as awaiting processing. Now the transaction is on the network, but it’s not yet confirmed or recorded on the blockchain.
Network Propagation. The first node to receive your transaction broadcasts it to other nodes. Each node that gets the transaction checks it for protocol compliance and ensures the transfer meets all requirements.
Validation. If all nodes accept the transaction as valid, it moves from the general queue to a special pending group. These transactions are ready for inclusion in a block and subsequent recording on the blockchain. If issues are found, you’ll get a notification and your funds remain in your account.
Block Inclusion. At this point, a miner (in Bitcoin) or validator (in Ethereum) chooses your transaction from the mempool, adds it to a new block with other transactions, and writes it to the blockchain. Transaction selection usually depends on the fee—the higher the fee, the more likely your transaction is included quickly.
Block Propagation. After the miner or validator adds your transaction to a block and records it on the blockchain, the new block’s details are broadcast to all network nodes. Each node receives the block’s data and the list of included transactions.
Mempool Cleanup. Once nodes receive the new block’s information, they remove any included transactions from their mempools. Your transaction no longer needs to be in the mempool—it’s now permanently on the blockchain.
Completion. The transfer is now fully complete—your friend has received the 0.01 BTC. The transaction is part of the blockchain’s immutable history and can be viewed in any blockchain explorer.
Mempool overload happens during periods of high network activity, when the number of requested transactions far exceeds what can fit in a single block. This can significantly impact transaction speed and fees.
Several key factors can slow or overload the mempool:
Network Congestion. A surge in transactions creates a shortage of space in each block, which is the primary cause of mempool overload. For context: a Bitcoin block holds about 3,150 transactions on average. If the mempool’s backlog greatly exceeds this—especially for hours at a time—the network becomes severely congested. Users then must either pay higher fees for faster processing or wait much longer.
Events and News. Events and news that impact the blockchain and crypto markets can spark sudden spikes in transaction activity. Examples include new token launches, major airdrops (free token distributions), celebrity or corporate endorsements, and significant tech upgrades. Any of these can quickly drive up transaction demand, overloading the mempool.
Forks and Network Upgrades. Major blockchain changes—like hard forks or large protocol upgrades—can cause temporary but severe mempool overload. During these events, many nodes are busy updating software and adapting to new rules, reducing their transaction-processing capacity and leading to a backlog.
Understanding these causes is essential for blockchain developers, who can proactively implement technical improvements—such as increasing block size, optimizing transaction processing algorithms, or deploying Layer 2 solutions—to reduce the negative impact of overloads on end users.
One of the most important factors affecting the order and speed of transactions in the mempool is the fee a user is willing to pay. This mechanism plays a central role in allocating blockchain network resources.
Miners and validators—who create new blocks—have the discretion to choose which transactions from the mempool to include. Their decision is primarily driven by economics: they select transactions that offer the highest potential profit from fees. This creates a natural market-based prioritization system.
Put simply, the higher the fee a user offers, the faster their transaction is processed and included in the blockchain—especially during network congestion.
So, the answer to the common question—how long does it take for a Bitcoin or other crypto transaction to confirm?—comes down to two main factors: the current mempool load and the fee you offer.
In an ideal scenario with a lightly loaded network and a small mempool, even minimal-fee transactions are processed quickly—usually within minutes or in the next block. If you offer a high fee in such conditions, your transaction is almost certain to be included in the very next block.
However, when the mempool is overloaded, the situation changes. If the network is busy and the mempool is crowded, a low-fee transaction may sit unconfirmed for hours or even days. During these times, miners and validators prioritize high-fee transactions, and low-fee ones remain in the mempool until the load subsides.
Practical tip: Many modern crypto wallets offer dynamic fee estimation tools based on the current state of the mempool. Using these helps you balance speed and cost. There are also analytics platforms where you can monitor network congestion, average fees, and estimated confirmation times for different fee levels in real time.
A mempool is a temporary holding area for unconfirmed transactions in a blockchain. It queues transactions for block inclusion and helps keep transaction processing orderly across the network.
The mempool directly affects both. When network activity is low, transactions confirm quickly and fees are lower. When the mempool is full, confirmations slow down and fees rise due to competition.
Transactions are delayed by low fees. You can speed them up by increasing the fee. Higher fees encourage validators to process your transaction sooner.
The mempool is a queue of unconfirmed transactions waiting for block inclusion. The blockchain is a distributed ledger of all confirmed transactions. The mempool holds temporary data; the blockchain is the permanent record.
Miners and validators choose transactions based on fee size. Higher-fee transactions are included faster, as they provide greater rewards. The selection algorithm optimizes both block size and profitability.











