The mempool (memory pool) is the waiting area where blockchain nodes temporarily hold transactions that have been broadcast but not yet packed into a block. After you send a transaction, it doesn't go on-chain instantly but first queues in each node's mempool, waiting to be picked and packed into the next block by a miner or validator. Because the mempool is publicly visible — who paid a higher fee, who might get prioritized — this is also why phenomena like fee-bumping to jump the queue, MEV, and front-running occur.
Full Explanation+
01 · What is this?
The mempool (short for memory pool) is the waiting area where blockchain nodes temporarily store transactions that have been broadcast but not yet packed into a block. To understand it, first remember a key fact: after you hit confirm transaction in your wallet, that transaction isn't completed on-chain instantly, but is first sent to the mempool of each node on the network, queuing alongside thousands of other pending transactions, waiting to be picked by a miner or validator and packed into the next block. In short, the mempool is the blockchain's waiting room — before a transaction boards (enters a block), it waits here. Understanding this waiting area lets you see why a transaction shows pending and why bumping the fee speeds it up.
02 · Why does it exist?
How is a transaction processed in the mempool? The key is the fee. The mempool holds a large number of transactions waiting to be packed, and each block can hold only a limited amount, so miners or validators naturally tend to prioritize transactions paying higher fees — because that's their income. This forms an auction-like mechanism: when the network is congested and everyone scrambles to get on-chain, the higher the fee (gas) you pay, the more likely you're prioritized and the faster you go on-chain; pay too little and your transaction may be stuck in the mempool for a long time, even unable to get in line. This is why many wallets let you speed up a transaction — essentially raising the fee so your transaction jumps forward in the mempool queue. Grasp this and you'll know to use low fees to save when not in a hurry, and high fees to rush when you are.
03 · How does it affect your decisions?
The mempool has an often-overlooked but hugely consequential property: it's publicly visible. On most blockchains, anyone can see all pending transactions not yet on-chain in the mempool — including what you intend to do and how much fee you paid. This public waiting is the root of many advanced phenomena. Professional bots continuously watch the mempool, and once they spot a profitable transaction (such as a large swap that will move the price), they insert their own transaction before or around yours with a higher fee — the operating basis of front-running, sandwich attacks, and MEV broadly. So the mempool isn't just a technical detail; it directly bears on whether your transaction gets seen and taken advantage of by others, especially when you make large or price-sensitive operations.
04 · What should you do?
Understanding the mempool helps you solve and avoid several practical problems. First, reading a stuck/pending transaction: a transaction that won't complete is usually not broken but stuck unable to get in line because the fee is too low; the fix is typically your wallet's speed-up function to raise the fee, or patiently waiting for an uncongested moment to be packed naturally. Second, understanding speed-up and cancel: both functions essentially send another transaction with the same nonce but a higher fee to override the stuck one. Third, being wary of MEV risk: because the mempool is public, large or price-sensitive transactions are easily targeted by bots, which is why some tools offer private transaction channels so your transaction bypasses the public mempool and avoids front-running. Keep these in mind and you can make the right call when a transaction is stuck or when doing large operations.
Real-World Example+
Understand the mempool with a congestion scenario. Suppose right now a hot NFT is launching on some chain, and thousands of people across the network scramble to send transactions at once, severely congesting it.
Meanwhile you also send an ordinary transfer, using your wallet's default normal fee level. After your transaction is broadcast, it queues in the mempool — but right now the mempool is packed with transactions willing to pay sky-high fees to grab the NFT. When miners pack the next block, they naturally prioritize the high-fee ones, leaving your normal-rate transaction aside, unable to get its turn, with your wallet showing pending the whole time.
You have two options: one, wait patiently for the buying frenzy to pass and the mempool to clear, and your transaction will be packed naturally; two, use your wallet's speed-up function to raise this transaction's fee, effectively jumping forward in the mempool queue so miners will prioritize it.
This scenario shows three things: a transaction waits in the mempool before going on-chain, packing order is largely decided by fee, and why bumping the fee speeds things up. Understanding the mempool, you won't be at a loss when a transaction is pending — you'll know it's usually just a matter of fee and congestion, not that your money has vanished.
Diagram
Feel free to share. Please credit the source.
Common Misconceptions+
✕ Misconception 1
× Misconception 1: A transaction is complete and on-chain the moment you hit confirm in your wallet. Wrong. Hitting confirm only broadcasts the transaction; it then first enters the mempool to queue, waiting to be packed into a block by a miner or validator and to accumulate enough confirmations before it's truly complete. While it still sits in the mempool, it can in theory be sped up or canceled.
✕ Misconception 2
× Misconception 2: The mempool is private, and only miners can see my pending transaction. Quite the opposite. On most public chains the mempool is public, and anyone (especially MEV bots) can see the content and fee of not-yet-on-chain transactions. This is precisely why front-running and sandwich attacks exist; to avoid them you need a private transaction channel that bypasses the public mempool.
The Missing Link+
Direct Impact
The mempool design reflects a core trade-off of public blockchains: transparency versus exploitability. The upside is that a public mempool makes the whole system highly transparent — anyone can verify pending transactions, estimate network congestion and what fee to pay, and the fee market runs as an open auction. But the cost is that this transparency also lays your transaction intent in the open, letting professional bots front-run and sandwich you, eating value that should have been yours. In other words, the mempool's openness is both an expression of the blockchain's trustless verifiability and a breeding ground for invisible costs like MEV. Understanding this trade-off gives you judgment about why private transaction channels exist and when to use them.
Generate Share Card
Crypto BibleGlossary
Intermediate
Mempool
記憶池
Mempool = the public waiting area for transactions sent but not yet on-chain
Your transaction first queues in the mempool, waiting to be packed into a block
Miners/validators often prioritize higher-fee transactions — paying more jumps the queue
The mempool is public, a breeding ground for MEV, front-running, and sandwich attacks
A stuck transaction is usually waiting too long in the mempool because its fee is too low
The Missing Link
Think your transaction goes on-chain the moment you send it? It first sits in the mempool, a public waiting area the whole world — bots included — can see, queuing to be packed.