A mempool, short for memory pool, is a node’s temporary set of valid transactions that have not yet been included in a block. The term is useful shorthand, but there is no single universal mempool shared identically by every node.
Nodes apply local validation, fee and resource policies, so two observers can see different pending transactions. Private relays and direct builder order flow may bypass a public view entirely. This covers Bitcoin and Ethereum transaction pools, fee selection, replacement and the limits of mempool-based trading signals.
Key Takeaways
Each node maintains its own pending-transaction pool under local software and policy rules.
A transaction can be valid for consensus but still rejected from a particular node’s mempool.
Bitcoin miners often consider fee rate in satoshis per virtual byte; Ethereum ordering also reflects nonce and builder economics.
A public explorer shows one service’s view, not every transaction waiting across the network.
What Is a Mempool?
When a user broadcasts a blockchain transaction, receiving nodes check its syntax, signatures, spendability and relevant policy rules. A node that accepts it may keep it in memory and relay it to peers while waiting for block inclusion.
The pool is not part of the confirmed blockchain. It can change when a block arrives, a conflicting transaction replaces an entry, a node restarts, an entry expires under local policy or resource limits force eviction.
A pending status therefore means “seen and retained by this service,” not guaranteed confirmation. See UEEx’s blockchain overview if the distinction between broadcast and confirmation is unfamiliar.
How Does the Bitcoin Mempool Work?
Validation and Policy
Bitcoin nodes verify that a transaction follows consensus rules before accepting it. They also apply relay and mempool policies designed to manage spam, fees and dependency chains. Policy can be stricter than consensus and can vary by node software or configuration.
A transaction rejected by one node may be accepted elsewhere. Miners also choose which accepted transactions to include, subject to block validity.
Fee Rate and Virtual Size
Bitcoin fees are commonly compared as satoshis per virtual byte, written sat/vB. Miners seeking fee revenue generally evaluate fee rate and package relationships rather than the absolute fee alone.
A large transaction may need a higher total fee than a small one to achieve the same sat/vB. “One satoshi per byte” is imprecise for modern Bitcoin fee analysis because witness data affects transaction weight and virtual size.
Dependencies and Packages
A child transaction can spend an unconfirmed parent. Nodes and miners may evaluate the fees and sizes of related transactions together. Child-pays-for-parent uses a higher-fee child to improve the package’s combined economics.
Replacement
A sender can sometimes replace an unconfirmed transaction with a conflicting one that pays a higher fee under the node’s replacement policy. Current Bitcoin software and miner policies should be checked directly; replacement behavior is not a universal promise from every participant.
How Does the Ethereum Transaction Pool Work?
Ethereum execution clients maintain local pools of pending transactions. A valid transaction includes a sender nonce, gas limit, fee fields, recipient or contract-creation data, value and signature.
Transactions from one account normally execute in nonce order. If nonce 10 is missing, a node may retain nonce 11 but it cannot be executed first. Wallets sometimes call this a queued rather than immediately executable transaction.
Under EIP-1559, a type-2 transaction sets a maximum fee per gas and a maximum priority fee. Inclusion depends on the block’s base fee, the effective tip, gas use, account balance, nonce and block-builder strategy. It is not a simple global queue sorted by one number.
How Do Public Pools, Private Order Flow and Application Queues Differ?
Queue type
Who can see it
Typical purpose
Limitation
Public node mempool
Peers receiving the transaction
Broad propagation before block inclusion
Views differ across nodes
Private relay
Selected relay, builder or validator participants
Privacy or execution protection
Requires trust in the service’s policy
Wallet queue
The wallet or provider
Tracks submitted account nonces
May not match network visibility
Exchange withdrawal queue
The centralized platform
Internal review before broadcast
Not a blockchain mempool
Private order flow can reduce public exposure but also concentrates visibility among intermediaries. Users should read the relay’s privacy, censorship and failure policy instead of assuming “private” means risk-free.
Why Do Transactions Remain Pending?
Fee Is No Longer Competitive
Network demand can rise after broadcast. In Bitcoin, the transaction’s fee rate may fall below the rate miners currently prefer. In Ethereum, the base fee can exceed the transaction’s maximum fee.
Nonce Gap or Conflict
An Ethereum transaction can wait behind an earlier nonce. A replacement with the same nonce can also cause different nodes or interfaces to display different candidates.
Parent Is Unconfirmed
A transaction that spends an unconfirmed output depends on its parent. Package limits or a low combined fee rate can delay both.
Local Eviction or Dropping
Nodes limit memory usage and apply expiration or eviction policies. A transaction can disappear from one node’s pool and remain known elsewhere. It can also be rebroadcast later if still valid.
What Are the Replacement and Fee-Bumping Options?
For Bitcoin, a compatible wallet may create a higher-fee replacement or use child-pays-for-parent when the user controls an appropriate output. The available method depends on the original transaction and network policy.
For Ethereum, a sender can submit a replacement using the same nonce and sufficiently higher fee settings. A “cancel” is usually another same-nonce transaction, often sending zero value to the sender. It is not guaranteed to win the race or reverse a transaction already included.
Never sign replacement instructions from an unsolicited support account. Verify the nonce, recipient, value and fee on the wallet’s trusted screen.
How Do Mempools Relate to MEV?
Public pending transactions can reveal swaps, liquidations and arbitrage opportunities. Searchers may submit competing transactions or bundles, while builders choose ordering that maximizes their objective.
This activity is often discussed as maximal extractable value, or MEV. A high gas price alone does not guarantee position because private bundles, proposer-builder relationships and protocol rules affect ordering.
See UEEx’s crypto order-book guide to distinguish a venue’s orders from blockchain transaction ordering. They are related during settlement but are not the same queue.
What Are Common Risks and Misinterpretations?
A mempool spike can signal demand, but it does not reveal one certain cause.
A large pending transfer is not proof of a sale, purchase or price direction.
Explorer fee estimates are forecasts based on one model and can be wrong.
Unconfirmed transactions can be replaced, dropped or invalidated by a conflict.
Private transactions may never appear in a public pending feed.
Front-running or copying a visible transaction can fail and still consume fees.
What Should You Check Before Trusting a Pending Transaction?
Confirm the network, recipient, value and transaction identifier.
Check whether the wallet reports broadcast, pending, safe or confirmed status.
Compare fee estimates from current network data, not an old screenshot.
For Ethereum, inspect the account nonce and fee cap.
For Bitcoin, inspect virtual size, fee rate and unconfirmed parents.
Use only wallet-supported replacement or acceleration tools.
Do not broadcast multiple conflicting fixes without understanding the result.
Wait for confirmations appropriate to the value and recipient’s policy.
Conclusion
A mempool is a local staging area, not a global waiting room or confirmation guarantee. Bitcoin and Ethereum nodes apply different data structures, fee rules and ordering constraints, while private flow can bypass public observation. Reliable analysis starts with the chain, node policy, fee unit, nonce or dependency structure and the difference between an estimate and a confirmed block.
Related Terms
Nonce – A sequential counter tied to an Ethereum account that determines transaction execution order.
Gas Fee – The payment required to have a transaction processed on an Ethereum-compatible network.
Replace-by-Fee (RBF) – A Bitcoin policy allowing an unconfirmed transaction to be replaced by one paying a higher fee.
Block Builder – An entity that assembles the set and order of transactions included in a proposed block.
Maximal Extractable Value (MEV) – Extra value a block builder or searcher can capture by including, excluding or reordering transactions.
UTXO– An unspent transaction output; the model Bitcoin uses to track spendable balances.
Is there one global mempool? No. Each node has its own view based on what it received and accepted under local policy.
Does a pending transaction mean the funds are gone? Not necessarily. The transaction is unconfirmed. Whether it can be replaced or eventually confirms depends on the chain, inputs, nonce and policy.
Can a miner include a transaction that my explorer does not show? Yes. The miner may have received it privately or through peers not observed by that explorer.
Are mempool transactions final? No. They are unconfirmed and can be dropped, replaced or invalidated by a conflicting confirmed transaction.
Why are fee estimates different? Services use different node views, historical windows, confirmation targets and models. All estimates are uncertain.
