Most people meet the mempool after something goes wrong.
A payment has not confirmed. A wallet says the fee is too low. Somebody insists the transaction was sent, but the recipient cannot see it. Bitcoin is working; the user just cannot see what it is doing.
mempool.space made that part of Bitcoin legible. It took data that used to look like node logs and turned it into projected blocks, transaction diagrams, fee ranges and a search box anyone can use.
The moving blocks are more than decoration
A mempool is the set of valid, unconfirmed transactions a Bitcoin node currently knows about. It is not one official global waiting room. Nodes can see slightly different transactions because of timing, configuration and relay policy.
mempool.space visualizes its view as blocks waiting to be mined. Higher-fee transactions tend to collect in the first projected block; lower-fee transactions sit deeper. That makes the block-space market obvious in a few seconds.
The projection is still an estimate. A miner may build a different template, receive transactions your explorer has not seen, accept an out-of-band payment, or simply find a block before your screen updates. “Next block” means competitive at the moment, not guaranteed in ten minutes.
This is the right way to use its fee recommendations: look at the depth, decide how soon you actually need confirmation, then set a rate. Do not blindly choose “high priority” every time, and do not assume the cheapest visible rate will clear on your schedule.
What a transaction page tells you
Paste a transaction ID into the search box and mempool.space shows whether the transaction is pending or confirmed, the fee rate, total fee, size, inputs, outputs and confirmation history. For a pending transaction, the page also shows its place in the current fee market.
That view helps answer practical questions:
- Was the transaction broadcast at all?
- Did it confirm, or is it still sitting in a mempool?
- Was the fee rate reasonable when it was sent?
- Is Replace-by-Fee available?
- Is a parent or child transaction affecting the package's effective fee rate?
The project goes well beyond one transaction page. It includes mining and Lightning dashboards, block audits, RBF history, APIs, test networks and Liquid views. The interface keeps getting deeper without making the basic search flow harder.
The best feature is that you can leave
The hosted website is convenient, but the Mempool Open Source Project is AGPL-licensed and designed to be self-hosted. It supports one-click installs on several Bitcoin node platforms, plus Docker and manual deployments for people who want more control.
That matters for privacy. Looking up one of your addresses or transaction IDs on a public explorer tells the operator that your IP address is interested in that data. Broadcasting through a public endpoint can link your network connection to the transaction as it first propagates.
A private instance connected to your own node removes the public query. It also lets you compare the explorer against a node you control instead of treating somebody else's website as an oracle.
Running Mempool does not replace Bitcoin Core. The node validates blocks and transactions. Mempool gives you a much better window into what that node knows.
A small COLDCARD PushTx win
COLDCARD's NFC PushTx format is deliberately simple. After signing, the COLDCARD encodes the complete transaction and a checksum into a URL. Tap an NFC phone and it opens that URL in the browser.
mempool.space implemented the public format at mempool.space/pushtx. Its page decodes the transaction, checks the checksum, broadcasts it, then opens the transaction page so the user can watch it enter the mempool and confirm.
The transaction is carried after the # fragment in the URL, so it is not included in the browser's first request for the page. The browser still has to submit the transaction for broadcast, and the public service can see the phone's network connection. Use a self-hosted PushTx page or your own node when that association matters.
For a normal fully signed transaction, the relay cannot change a destination or amount without invalidating the signatures. It can fail to broadcast, log the request or refuse service. Transaction review still happens on the COLDCARD before signing.
This is small interop done correctly: a public specification, independent implementation, no required app, and a custom-server option for users who want it.
Use it without outsourcing judgment
A block explorer reports one infrastructure stack's view of Bitcoin. It cannot tell you who controls an address, guarantee when a miner will include a transaction, or make a bad transaction safe. Never enter a seed phrase, private key or wallet backup into any explorer.
Use the public site to learn how block space behaves. Use it to check a transaction and understand fees. When privacy or verification matters, run the project beside your own node.
mempool.space made Bitcoin easier to inspect without making it less Bitcoin. That is a project worth highlighting.