What Is the Mempool? Where Ethereum Transactions Wait

The mempool (short for "memory pool") is the collection of pending, signed Ethereum transactions that have been broadcast to the network but not yet included in a block — effectively a waiting room where transactions sit, visible to the network, until a validator selects them for inclusion in an upcoming block.

How transactions get there and what happens next

When you sign a transaction in your wallet and hit send, it doesn't go directly to a single, central place. Instead, it's broadcast peer-to-peer: your node (or your wallet's RPC provider) shares it with the nodes it's connected to, which each share it with their own connections, and so on, until it's propagated widely across the network. Each node maintains its own local copy of the mempool — meaning there isn't one single, universally identical mempool everyone sees, though in practice, well-connected nodes converge on very similar views within seconds.

From there, a validator assigned to propose the current slot selects transactions from the pending pool to include in their block, generally prioritizing by the fee offered (specifically the priority fee, or tip, under EIP-1559), since a higher tip is more profitable for whoever proposes the block. Transactions with low fees relative to current network demand can sit in the mempool for an extended period, waiting for network congestion to ease or eventually being replaced or dropped.

Public versus private mempools

There are effectively two channels transactions can travel through:

• The public mempool. Broadcast openly and visible to anyone running a node or monitoring network traffic — including automated bots specifically watching for profitable opportunities.
• Private transaction relays. Some infrastructure lets users submit transactions directly to a block builder or a small set of trusted relays, bypassing the public mempool entirely, so the transaction only becomes visible once it's already included in a block.

Aspect	Public mempool	Private relay
Visibility before inclusion	Visible to the entire network	Hidden until included in a block
Exposure to front-running	Higher	Lower
Availability	Default for most wallets	Requires specific RPC/wallet support
Typical use case	Everyday transactions	Larger trades, sensitive orders

Why the mempool matters for MEV and front-running

Because pending transactions in the public mempool are visible before they're confirmed, automated searchers can observe a profitable-looking pending transaction — say, a large DEX swap that will move a pool's price — and attempt to insert their own transaction ahead of (or around) it to capture value from the resulting price movement. This general category of value extraction is called MEV (maximal extractable value), and the specific pattern of exploiting visible pending transactions is called front-running, covered in detail in our companion piece.

The mempool's openness is a double-edged design: it's part of what makes Ethereum permissionless and transparent (anyone can see and, in principle, include any valid pending transaction), but that same openness is precisely what enables searchers to observe and act on other users' pending intentions before they're finalized.

Practical implications for users

• Large or price-sensitive trades are more exposed to front-running risk when sent through the public mempool, since the pending transaction reveals the trade's direction and size before it executes.
• Setting appropriate slippage tolerance on swaps helps limit how much a front-running attack (or ordinary price movement) can cost you, at the expense of potentially failing during fast-moving markets if set too tight.
• Private RPC or relay options, where available, reduce mempool visibility for sensitive transactions, though they shift trust toward whichever relay or builder is handling the transaction privately instead.
• Failed or stuck transactions are also a mempool phenomenon — a transaction with too low a fee can sit pending for a long time, and wallets typically offer a way to "speed up" (rebroadcast with a higher fee) or cancel (send a conflicting transaction with the same nonce and a higher fee) a stuck one.

Mempool eviction and replacement rules

Nodes don't keep every pending transaction forever — mempools have limited capacity, and nodes apply local rules to decide what to keep. Transactions offering fees too low relative to current demand may simply be dropped after a period if better-paying transactions keep arriving and space is limited. Ethereum also enforces a specific replacement rule: to replace your own pending transaction (whether to speed it up or cancel it), the replacement must reuse the exact same nonce and offer a meaningfully higher fee — typically at least a modest percentage increase — otherwise nodes will simply ignore it and keep relaying the original. This prevents a cheap, low-effort way of spamming the network with near-identical replacement attempts.

Mempool visibility differs by node

It's worth being precise that there isn't a single canonical mempool anyone can query with perfect accuracy. Each node builds its own local view based on which transactions it has actually received from its peers, and differences in network topology, latency, and connectivity mean two nodes queried at the same instant can show slightly different pending transaction sets. Block explorers and wallet "pending transaction" displays are typically pulling from one or a handful of specific nodes or RPC providers, which is a reasonable approximation of the broader network's state but not a perfectly authoritative one.

Bottom line

The mempool is the visible, distributed staging area where Ethereum transactions wait after being signed and broadcast, but before a validator includes them in a block — a necessary part of how a permissionless, decentralized network coordinates who gets included and when. That same visibility is the root cause of front-running and broader MEV extraction, which is why sensitive or large transactions increasingly route through private relays instead of the fully public mempool when minimizing that exposure matters.