What Is a Mempool? How Pending Transactions Work (2026)

If you’ve ever sent a Bitcoin transaction and watched it sit “pending” for an hour — or a whole day — you’re not alone. That stuck transaction isn’t lost, broken, or eaten by the network. It’s almost certainly sitting in one place: the mempool. Understanding this single concept turns frustrating waits into predictable, manageable outcomes.

In this guide, you’ll learn what a mempool actually is, how transactions flow through it, how fees and congestion interact to determine your confirmation time, how to read congestion like a pro, and the practical tricks — including replace-by-fee and child-pays-for-parent — that can rescue a stuck transaction. By the end, you’ll time your transactions with confidence instead of guessing.

id=”what-is-a-mempool”>What a Mempool Actually Is

The mempool — short for “memory pool” — is a waiting room for unconfirmed transactions. Every full node on the Bitcoin network keeps one. When you broadcast a transaction, it doesn’t go straight into a block. Instead, each node checks that it’s valid, then holds it in its mempool until a miner picks it up and includes it in a mined block.

Here’s the detail most beginners miss: there isn’t one single mempool. Each node maintains its own, and while they overlap heavily, they’re never identical. A transaction your wallet shows as “broadcast” may have reached thousands of nodes in seconds, or it may still be propagating. This is why two block explorers can sometimes disagree for a minute or two about whether your transaction exists — they’re reading different nodes’ mempools.

Think of it like a train station. Blocks are trains that leave roughly every 10 minutes and have a fixed number of seats (about 4 megabytes of block weight). Your transaction is a passenger on the platform. The mempool is the platform — a visible, public queue that everyone can inspect. You can see how many passengers are waiting, how much each is “paying” for priority boarding, and make an informed guess about when you’ll get a seat.

One more important fact: mempool contents are temporary. A node can drop a transaction from its mempool if it sits too long (most nodes evict transactions after about two weeks), if the node restarts, or if a higher-fee version of the same transaction replaces it. A dropped transaction doesn’t mean your coins are gone — the coins never left your wallet until the transaction is confirmed. It just means the transaction attempt faded out of the waiting room and you may need to rebroadcast or replace it.

If you’re new to wallets and addresses generally, our walkthrough of how to set up a Bitcoin wallet covers the basics that make everything below easier to follow.

How the Mempool Works, Step by Step

Let’s trace a transaction’s full journey so the mempool’s role clicks into place.

Step 1 — You sign and broadcast. Your wallet constructs the transaction, you approve it, and the wallet sends it to the peers it’s connected to. This takes seconds.

Step 2 — Nodes validate and relay. Each receiving node runs the transaction through Bitcoin’s consensus rules: Are the inputs real and unspent? Are the signatures valid? Is the fee above the node’s minimum relay threshold? If it passes, the node stores it in its mempool and relays it to its own peers. Within roughly 10–30 seconds, your transaction has usually propagated across most of the network.

Step 3 — Miners pick the most profitable set. Miners (or mining pools) don’t take transactions first-come-first-served. Their software sorts the mempool by fee rate — typically measured in satoshis per virtual byte (sat/vB) — and builds the most profitable block template possible. High-fee transactions get picked first. This is the single most important dynamic in the whole system, and it’s why fee choice matters more than anything else you can control.

Step 4 — Confirmation and cleanup. When a block is mined, every transaction in it is removed from every node’s mempool. Your wallet sees the first confirmation. Each subsequent block buries it deeper, making reversal practically impossible.

There are two edge cases worth knowing. First, if two conflicting transactions enter the mempool (a double-spend attempt), nodes keep only the first one they saw — unless the replacement follows the opt-in replace-by-fee rules, which we’ll cover shortly. Second, during extreme congestion, nodes with limited memory start evicting the lowest-fee transactions first. A transaction with a fee below a node’s minimum may never even enter that node’s mempool — it’s rejected at the door.

How Fees Interact With the Mempool

Fees are the language of the mempool. Because block space is scarce and demand fluctuates, Bitcoin runs a continuous, decentralized fee auction. Understanding the mechanics of that auction saves you real money.

Fee rate, not fee total. What matters is not how much you pay in total, but how much you pay per unit of block space — satoshis per virtual byte (sat/vB). A simple one-input, two-output transaction might be ~140 vBytes; at 10 sat/vB that’s 1,400 sats. A complex transaction with many inputs could be 1,000 vBytes and need 10,000 sats at the same rate. Wallets that quote a flat fee without showing the rate are hiding the number that actually determines your confirmation speed.

The fee market in action. When the mempool is nearly empty, even 1–2 sat/vB gets you into the next block. When it’s congested — say, during a price surge when everyone is moving coins to exchanges — the cutoff for the next block can spike to 50, 100, or even several hundred sat/vB. Same transaction, wildly different price, purely because of demand. This is why a transaction that confirmed in 10 minutes last month might take 10 hours this week if you reuse the same fee.

What your wallet is actually doing. Modern wallets estimate fees by looking at recent mempool data: what fee rates got into the last several blocks, and what’s currently waiting. A “fast / medium / slow” slider is just packaging for three points on that distribution. The estimates are good but not perfect — a sudden wave of new transactions can invalidate them within minutes. If speed matters, check a mempool visualizer yourself before sending (type the address into your browser rather than clicking links from strangers — more on that in the scams section).

Two rescue tools: RBF and CPFP. If you underpaid and your transaction is stuck, you have options. Replace-by-fee (RBF) lets you rebroadcast the same transaction with a higher fee, as long as you opted in when you first sent it — most good wallets enable this by default now. Child-pays-for-parent (CPFP) works even without RBF: you spend the unconfirmed output in a new “child” transaction with a generous fee, and miners, wanting the child’s fee, are forced to confirm the “parent” first. Both are legitimate, built-in mechanisms. For a deeper walkthrough of low-cost sending strategies, see our guide on how to send Bitcoin with low fees.

How to Read Mempool Congestion

Mempool visualizers turn the waiting room into a picture: usually stacked colored bands showing how many megabytes of transactions are waiting at each fee level. Learning to read one takes five minutes and pays off every time you transact.

What the bands mean. Each band represents transactions at a given fee range. The bottom bands (low fees) are the “economy” queue; the top bands (high fees) are the express lane. A block clears roughly the top ~4 MB of weight. So if the chart shows 2 MB waiting above 20 sat/vB and 30 MB waiting below it, a 20 sat/vB transaction is likely next-block material while a 5 sat/vB one could wait a long time.

Projected blocks. Most visualizers show “projected blocks” — how many future blocks it would take to clear each fee band. If your fee sits in the “next block” band, expect ~10 minutes. If it’s in the “+5 blocks” band, budget an hour or more. Treat these as estimates, not promises: new transactions arrive constantly and can push you back.

Patterns to recognize. Congestion follows rhythms. Weekends and quiet overnight hours (UTC) are often cheap. Big price moves, exchange listing announcements, and NFT-style inscription waves create spikes. There’s also a weekly cadence to mining itself — blocks average 10 minutes but variance is real, and a streak of slow blocks can make even a calm mempool feel congested. If your transaction isn’t urgent, waiting 12–24 hours for a quiet window routinely cuts fees by half or more.

What “stuck” really means. A transaction with a competitive fee that hasn’t confirmed after 30–60 minutes usually just means block variance or a fresh demand wave — give it time. A transaction with a fee far below the current cutoff sitting unconfirmed for days is genuinely stuck and a candidate for RBF or CPFP. And a transaction that vanishes from explorers after a week or two was likely evicted from mempools — your coins are safe; you can simply send again. Our guide on how to speed up a Bitcoin transaction walks through the rescue options in detail.

Practical Tips for Timing Your Transactions

You can’t control the mempool, but you can work with it. These are the habits that experienced users rely on.

Check before you send. Make it a 30-second habit: glance at a mempool visualizer before any non-urgent transaction. If the next-block fee is 80 sat/vB and your transfer can wait, note it and check again in a few hours. Fee spikes are often sharp and short-lived.

Batch and consolidate. Every input adds size to your transaction, and size is what you pay for. If your wallet holds many small UTXOs (unspent outputs), a future spend will be large and expensive. Consolidating small UTXOs into one output during a low-fee period is like buying block space wholesale — it makes all your later transactions cheaper. Conversely, avoid creating dust outputs you’ll have to consolidate later.

Use the right address type. Native SegWit (bc1q…) addresses produce smaller transactions than legacy (1…) addresses, which means lower fees at any given fee rate. If your wallet still defaults to legacy addresses, switching is one of the simplest fee cuts available.

Enable RBF by default. There’s no downside for most users: it just gives you the option to bump the fee later. Check your wallet’s settings — in many wallets it’s a toggle buried under “advanced” options.

Don’t overpay out of anxiety. The “fast” preset in wallets often overshoots, especially right after a spike begins. If your transaction can wait an hour, the “medium” or even “economy” option usually confirms fine — and the savings compound if you transact regularly. The exception: time-sensitive moves like exchange deposits ahead of a trade, where paying for the next block is simply the cost of doing business.

Plan around known events. Major protocol upgrades, widely anticipated launches, or days when large known entities move coins can all jam the mempool. You don’t need to predict these perfectly — just avoid sending large, fee-sensitive consolidations on days when crypto Twitter is on fire.

Common Mempool Myths and Mistakes

Myth: “My transaction is lost because it’s unconfirmed.” Unconfirmed is not lost. Until a transaction is mined into a block, your coins remain under your control. The worst case for a stuck transaction is inconvenience and, rarely, needing to rebroadcast or replace it.

Myth: “Higher total fee always means faster confirmation.” Miners sort by fee rate (sat/vB), not total fee. A 10,000-sat fee on a huge 2,000-vByte transaction (5 sat/vB) loses to a 3,000-sat fee on a tiny 100-vByte transaction (30 sat/vB) every time.

Myth: “The mempool is the same everywhere.” As noted earlier, each node has its own mempool with its own size limits and eviction policies. Minor discrepancies between explorers are normal and not a sign of a problem.

Mistake: Sending without checking during a spike. The classic expensive error is firing off a wallet’s default fee during a demand surge. Thirty seconds on a visualizer would have shown the spike. Build the habit.

Mistake: Disabling RBF to “keep it simple.” Simplicity now can mean helplessness later. RBF costs nothing until you use it, and it’s the cleanest rescue tool you have.

Mistake: Trusting “accelerator” services that ask for private keys. No legitimate service needs your seed phrase to accelerate a transaction. Anyone asking for it is running a theft operation, full stop.

Frequently Asked Questions

The Bottom Line

The mempool is Bitcoin’s public waiting room: a per-node pool of unconfirmed transactions that miners draw from, highest fee rate first. Your fee rate in sat/vB is the main thing you control, congestion follows predictable rhythms you can check in seconds, and tools like RBF and CPFP mean a stuck transaction is a solvable problem, not a lost one.

Build the 30-second habit of checking congestion before you send, keep RBF enabled, consolidate UTXOs when fees are low, and never hand your seed phrase to anyone promising to “accelerate” your transaction. Do that, and the mempool goes from a source of anxiety to a system you can read and use to your advantage.

This guide is for education only — not financial advice.