Mempools
Understand how pending transactions are held before block inclusion, why mempools differ between nodes, and how congestion affects fees and execution.
Reading progress — saved on this device
A mempool is a node’s working set of valid transactions that have been seen by the network but have not yet been included in a block. It is best thought of as a dynamic waiting area, not a single global queue.
There is no one universal mempool
Each node can maintain its own view based on the transactions it has received and its local policy. Two nodes may temporarily have different pending sets because of propagation delays, fee filters, size limits or replacement rules.
The transaction journey
Sign
The user signs a transaction with the relevant private key.
Broadcast
The transaction reaches one or more network nodes.
Pending
Nodes validate basic rules and may keep it in their mempool.
Included
A block producer selects it and it leaves the pending set after block acceptance.
Fees and prioritisation
When block space is scarce, producers commonly prioritise transactions offering greater economic reward. The exact mechanism varies by network. A low-priority transaction may remain pending longer, be replaced, or eventually be dropped by some nodes.
| Condition | Typical effect |
|---|---|
| Low congestion | Broader range of fees can clear promptly. |
| High congestion | Fee estimates rise and low-priority transactions may wait. |
| Sudden demand spike | Wallet estimates may lag and previously adequate fees can become uncompetitive. |
Replacement, cancellation and nonce issues
Some networks support transaction replacement or “speed up” workflows. These usually work by submitting a new transaction that competes with the pending one under protocol-specific rules. On account-based networks, nonce sequencing can also cause later transactions to wait behind an earlier stuck transaction.
Why mempools matter to traders
- They provide an early view of transaction demand before settlement.
- Congestion can delay collateral movements and exchange deposits.
- Public pending transactions can create information leakage and ordering risks in DeFi.
- Fee spikes can turn a small on-chain trade or transfer uneconomic.
Knowledge check
- What is the core function described in this lesson?
- Which part of the process can create delays or uncertainty for a trader?
- What information would you verify before sending or acting on a transaction?
Common questions
If a transaction is in a mempool, is it guaranteed to confirm?
No. Pending transactions can remain unconfirmed, be replaced, become invalid, or be dropped from nodes depending on the network and circumstances.
Can everyone see the mempool?
On many public networks much pending activity can be observed, but not every node has the same view and some transaction-routing systems can bypass the public mempool.
Why can a transaction disappear and later reappear?
Nodes can drop transactions locally because of memory policies or changing validity conditions, while other peers may still retain and rebroadcast them.
Summary
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →