Limited time: $9 launch price · Get the full ebook
Fundamentals

What Is the Bitcoin Mempool? A Beginner's Guide to How Transactions Wait in Line

Every Bitcoin transaction passes through a global waiting room called the mempool before it ends up in a block. Understanding the mempool tells you why fees spike, why your transaction sometimes hangs, and how to fix it.

By The BitcoinHomeBase Team · Updated 2026-05-08 · 10 min read

Send a Bitcoin transaction. Watch the wallet say ‘Pending.’ What is actually happening during those minutes — or, occasionally, hours? The answer is the mempool. Once you understand it, three different beginner mysteries solve themselves at once: why fees go up and down, why some transactions take ages to confirm, and why people who run their own Bitcoin nodes seem to know things you do not.

This article is the plain-English explanation of the mempool: what it is, how to read one, and what it means for you when you send Bitcoin in 2026.

What the mempool actually is

The mempool (short for ‘memory pool’) is the global waiting room for unconfirmed Bitcoin transactions. When you click Send, your wallet broadcasts the transaction out to the network. Every Bitcoin node that hears about it adds the transaction to its own local mempool — the list of transactions it knows about that have not yet been included in a block.

There is no single mempool. Each of the roughly 17,000 active Bitcoin nodes keeps its own copy. They are all roughly synchronized within seconds, but they can disagree at the edges. When you look at a website like mempool.space, you are looking at the mempool of one specific node that the website operates — a representative view of what most miners are seeing.

Transactions sit in the mempool until a miner picks them up and includes them in a block. Once they are in a block, they have one confirmation, they leave the mempool, and they are now part of the permanent Bitcoin ledger. (Our piece on how to read a block explorer covers what happens after the mempool exit.)

How miners pick transactions: the fee market

A new Bitcoin block goes out roughly every 10 minutes on average. Each block can hold a limited amount of transaction data — in practice, about 4 megabytes of weight, which corresponds to roughly 2,000–4,000 average transactions per block depending on what kinds of transactions they are.

If the mempool has more transactions than will fit in a block, miners need to choose. They choose by picking the transactions that pay the highest fee per byte of data. Not the highest total fee — the highest fee per byte. A small transaction paying $1 in fees might get included before a large transaction paying $5, because the small one pays more per byte.

This creates a real-time auction. When mempool demand is high, fees spike, because users compete by raising what they will pay. When demand drops — say, on a Sunday afternoon when the Asian markets are quiet — fees plummet, because there is no competition and even the cheap transactions get into blocks. (Our deeper piece on Bitcoin network fees goes through how to set the right fee for your situation.)

Reading a mempool explorer in 90 seconds

The standard tool is mempool.space, a free public site. Visit it and you will see a multi-colored block diagram on the right of the screen. Here is how to read it:

Two practical signals to look for. First, the fee number on the next-block square is the ‘ASAP’ rate — pay that or higher and you confirm in the next 10 minutes. Second, if the upcoming-block stack is empty (just one or two future blocks shown), the mempool is light and even a low fee will confirm quickly.

Why your transaction is ‘stuck’

The most common beginner experience is sending a Bitcoin transaction at a too-low fee, then watching it sit in ‘Pending’ for hours. The wallet did not break. The transaction is just sitting at the bottom of the priority pile, waiting for a moment when the mempool empties enough that low-fee transactions get scooped up. That moment may come tonight. It may come in three days. It may technically never come, if the fee is so low that newer, slightly higher-paying transactions keep cutting in line.

Each Bitcoin node will eventually drop a stuck transaction from its mempool after about two weeks of no progress — this is called ‘eviction.’ Once that happens, the transaction has effectively never happened, and the coins are spendable again from your wallet. So nothing is permanently broken, but you can be in limbo for a while.

The fix is not to wait. The fix is to bump the fee on the existing transaction or replace it. Two methods exist: Replace-By-Fee (RBF), which lets you send a new version of the same transaction with a higher fee that miners prefer, and Child-Pays-For-Parent (CPFP), which sends a new transaction that spends the output of the stuck one with a high enough fee that miners will pull both into the block. Most modern wallets handle this with one click. Our walkthrough on how to fix a stuck Bitcoin transaction covers it step by step.

What sets fee rates day to day

Three things drive whether the mempool is congested or empty on any given day:

1. Bitcoin price action.

When the price is moving fast, more people are sending Bitcoin to and from exchanges — either to take profit or to deploy fresh capital. Volume up, mempool up, fees up. Quiet sideways markets produce the cheapest fees because nobody is moving anything in a hurry.

2. Inscription and ordinal traffic.

Since 2023, Bitcoin has had a class of usage called inscriptions / Ordinals — people storing image and text data inside Bitcoin transactions. When an inscription craze hits (it happens periodically), it can clog the mempool with thousands of large, low-priority transactions. This drives up fees for everybody. Look at the ‘Ordinals percentage’ chart on mempool.space if fees seem unusually high without an obvious reason.

3. Miner behavior.

Miners want to maximize revenue per block, so they will pack the most fee-paying transactions in. But they also occasionally produce nearly-empty blocks — either because they found a block faster than expected after the previous one, or because they are running custom software (e.g. for political reasons, or as a service to a specific pool).

Why every node maintaining its own mempool is actually important

It is tempting to picture the mempool as one shared global queue. It is not. Each of the 17,000 nodes maintains its own. This matters for one reason that beginners eventually run into: privacy.

When you broadcast a transaction, your wallet's local node (or your wallet's chosen node, if you are using a public service) sends the transaction outward. The first node to see it could in theory log your IP address alongside the transaction — that is one of the few moments your real-world identity could be linked to a Bitcoin address by surveillance. Running your own node and broadcasting through it cuts that out: nobody outside your home sees the transaction first. Our deep dive on running your own Bitcoin node walks through the setup.

Practical takeaways

You do not need to think about the mempool every time you send Bitcoin. But three things are useful to keep in mind:

  1. Before you send, glance at mempool.space. Check the next-block fee. If you are not in a hurry and the rate looks high, wait until tomorrow morning — it will probably be lower.
  2. Always send with RBF enabled if your wallet offers it. This costs nothing if your transaction confirms quickly, and saves the day if you set the fee too low.
  3. Do not panic if your transaction sits at ‘Pending’ for an hour. Most modern wallets automatically estimate a fee that confirms within an hour. If yours does not, that is a sign to switch wallets.

The shortest possible summary

Once you have looked at a few mempools, the next time someone tells you Bitcoin fees are ‘crazy right now’ you will be able to check for yourself in 10 seconds and know whether they are right or just venting.