How to Read the Bitcoin Mempool

Every Bitcoin transaction spends a few minutes — sometimes hours — in a waiting room before it lands in a block. That waiting room is the mempool. Learning to read it is the single best way to know whether to send now or wait, and exactly what fee to pay. It looks intimidating at first, but it's really just a queue sorted by price. Here's how to make sense of it.

What the mempool actually is

The mempool (short for “memory pool”) is the collection of transactions that have been broadcast to the network but haven't been mined into a block yet. When you hit send, your transaction doesn't go straight into the blockchain — it goes into the mempool first, where it waits with everyone else's pending transactions. Miners then pick transactions out of that pool, roughly ten minutes at a time, and pack them into the next block.

The key thing to understand is howminers choose. Block space is limited, so miners take the transactions that pay the most per unit of space first. That's the whole game: the mempool is a queue, and your position in it is set by your fee — not by when you sent, or how much you're sending. If you want the full mechanics, see how Bitcoin fees work.

Mempool size: vMB and transaction count

The first number you'll see on a mempool explorer is its size, usually given two ways:

• →Virtual megabytes (vMB) — how much block space all the waiting transactions would take up. Since each block holds roughly one “block worth” of space, a backlog measured in dozens of vMB means many blocks' worth of transactions are queued ahead.
• →Transaction count — simply how many unconfirmed transactions are sitting in the pool.

Size matters because it tells you how deep the queue is. A near-empty mempool means almost anything confirms quickly and cheaply. A large backlog means low-fee transactions may sit for a long time — though, as you'll see below, a big backlog doesn't always mean the next block is expensive.

Fee bands: reading the fee market

Fees are quoted in sat/vByte — satoshis per virtual byte of transaction size. Because miners sort by this rate, the mempool naturally sorts itself into bands: a cluster of transactions paying 30+ sat/vByte, another paying 15–30, another at 5–15, and a long tail paying 1–5. Most explorers colour these bands so you can see at a glance where the demand sits.

Reading the bands tells you the shape of the market right now. If almost everything is bunched in the low bands, the network is quiet and a modest fee sails through. If there's a thick wall of high-fee transactions, demand is heavy and you'll need to pay up to keep pace — the situation behind why fees spike.

Pending blocks: the next few blocks, previewed

The most useful view on an explorer like mempool.space is the row of pending (projected) blocks. It shows the next several blocks — often about eight — before they've been mined, built out of the transactions currently waiting in the mempool. Each projected block displays the fee range it contains and a median sat/vByte.

Read it left to right. The leftmost block is the one miners are most likely to produce next, and it holds the highest-paying transactions. As you move right, each block contains progressively cheaper transactions — because the high-fee ones have already been “used up” by the earlier blocks. The fee range on each projected block is essentially a price menu: pay the rate shown on a given block and you can expect to land in roughly that block.

Reading “my transaction will be in block N”

Once your transaction is broadcast, you can paste its ID into an explorer and it will place you in the queue — often showing something like “expected in block 3.” That means two projected blocks are expected to be mined ahead of yours, so at normal ten-minute spacing you're looking at roughly half an hour, give or take.

Treat that number as an estimate, not a promise. The projection assumes no new higher-fee transactions flood in and bump you back, and that blocks arrive on their usual schedule — both of which vary. If new demand pushes you further down the queue and you can't wait, that's when tools like fee bumping come in. For a fuller picture of timing, see how confirmation works end to end in the fee guides.

Why a big backlog can still have cheap next-block fees

Here's the counterintuitive part that trips people up. You can see a mempool holding tens of vMB — a huge pile of transactions — and yet the next-block fee is low. How?

Because that backlog is mostly made of low-fee transactions sitting patiently in the cheap bands. Miners always fill the next block from the top of the fee market. If the high-fee bands are thin, the next block fills up with modestly-priced transactions and its required rate is low — even though millions of low-fee transactions are stuck below, waiting for demand to clear.

The practical lesson: don't judge the cost of sending by the total mempool size.A scary-looking backlog can coexist with a cheap next block. What decides your price is the top of the fee market — the projected blocks — not the length of the tail beneath it.

What all this tells you about when to send

• →Empty or thin mempool — send now at a low rate; almost anything confirms quickly.
• →Modest backlog, cheap projected blocks — send now, but pick a projected block that matches your patience instead of overpaying for block one.
• →Heavy demand across every band — if it isn't urgent, wait. Fees ease overnight and on weekends; see the cheapest time to send Bitcoin.

Reading the mempool turns fee-setting from a guess into a decision. You're not hoping a wallet's canned “fast / medium / slow” estimate is right — you're looking at the actual queue and choosing your spot in it.

The bottom line

The mempool is just a queue sorted by fee. Its size tells you how deep the backlog runs; the fee bands show where demand sits; and the projected blocks are a live price menu telling you what rate buys a spot in each of the next several blocks. Read those three things together and you'll always know whether to send now or wait — and exactly what to pay when you do.

Skip the manual reading and let the SatSaver tracker do it for you — it watches the live queue and tells you whether to send or wait, plus the exact sat/vByte to pay. Mempool data from mempool.space.