Mempool Space: How I Track Every Bitcoin Transaction Before It Confirms

Dear Diary,

I spent three hours last Tuesday watching a Bitcoin transaction sit in limbo. The fee was too low, the network was busy, and I had no idea where my money actually was. That frustration sent me down a rabbit hole, and I came out the other side with a tool I now use every single day: mempool.space.

What the Bitcoin Mempool Actually Is

Every Bitcoin transaction passes through a waiting room before it lands on the blockchain. That waiting room is called the mempool, short for memory pool. When you send BTC from your wallet, the transaction doesn’t go straight into a block. It gets validated by nodes on the network, then stored in their memory while it waits for a miner to pick it up.

Here’s the part that trips people up: there’s no single global mempool. Each Bitcoin node maintains its own copy. One node might hold 80,000 unconfirmed transactions while another holds 78,000. The contents overlap heavily, but they’re never identical. That’s why different block explorers sometimes show slightly different numbers.

Miners scan their mempool and build block templates by picking the transactions that pay the highest fee rate first. Fee rate is measured in satoshis per virtual byte, or sat/vB. When the network gets busy, this becomes a real-time auction. Users who want fast confirmation bid higher, and the rest of us wait.

How Mempool.space Shows You What’s Happening

Mempool.space turns all of that invisible queue data into something you can actually read. The homepage displays three main things. On the left, a treemap where each rectangle represents a pending transaction, sized by weight and colored by fee rate. In the center, projected blocks show which transactions miners are likely to include next. On the right, fee estimates break down into four priority tiers: High, Medium, Low, and No Priority.

When I checked today, High Priority sat at 2 sat/vB, while No Priority was at 1 sat/vB. That’s a quiet mempool. During peak congestion, I’ve watched High Priority climb past 100 sat/vB. The difference between checking fees before you send and just guessing can cost you thousands of sats.

The site also tracks mempool memory usage. Bitcoin Core allocates 300 MB by default for each node’s mempool. When usage approaches that cap, nodes start dropping the lowest-fee transactions. Mempool.space shows a “Purging” threshold on the front page. If your transaction’s fee rate falls below that line during congestion, it might not propagate across the network at all.

Tracking a Transaction and Fixing a Stuck One

Paste any transaction ID into the search bar and mempool.space shows you everything: fee rate, confirmation status, inputs, outputs, and where it sits in the queue. I use this constantly. When I send BTC from my hardware wallet, I grab the TXID and drop it into mempool.space to see if it’s moving or stuck.

If a transaction gets stuck, there are two main fixes. Replace-By-Fee, or RBF, lets you broadcast a replacement transaction with a higher fee. The original gets kicked out and miners see the new version instead. This only works if your wallet had RBF enabled when you sent the original. Most modern wallets like Sparrow, Electrum, and BlueWallet support it by default.

The second option is Child-Pays-For-Parent, or CPFP. You create a new transaction that spends the unconfirmed output, attaching a high enough fee to cover both transactions combined. Miners can’t confirm the child without confirming the parent, so both clear together. Mempool.space shows you the effective fee rate after CPFP adjustments, which takes the guesswork out of whether your fee bump worked.

The API and Why It Matters

Mempool.space exposes a free public API that doesn’t require an API key for low-frequency queries. The endpoint /api/v1/fees/recommended returns current fee estimates in JSON. I’ve set up a simple script that checks fees every ten minutes and pings me when they drop below 2 sat/vB, which is my signal to consolidate UTXOs cheaply.

The whole project is open source and self-hostable. If you run your own Bitcoin node, you can spin up a private instance for total privacy. The public site is convenient, but it does log your IP and the transactions you look up. For anything sensitive, self-hosting is the move.

Why I Check Mempool.space Before Every Transaction

The few seconds it takes to look at current fee conditions before hitting send has saved me real money. Weekend nights tend to be quieter. Market events and inscription activity can spike fees within hours. The mempool is a live auction, and mempool.space is the clearest window into that auction I’ve found.

I don’t send Bitcoin without checking it first anymore. Neither should you.