mempool.space (Self-Hosted Explorer)

mempool.space is an open-source block explorer and mempool visualizer maintained by The Mempool Open Source Project. It displays real-time and historical information about a Bitcoin node's mempool, renders pending transactions as projected blocks colored by fee rate, and lets users search and inspect transactions, addresses, and blocks. The public instance at mempool.space is one of the most-used explorers in Bitcoin, but the software is deliberately designed to be self-hosted — and for a sovereign operator, the self-hosted deployment is the one that matters.

Why self-host an explorer

The privacy argument is direct: every time you look up your own transaction on a public explorer, that operator learns an address you care about, your IP, and the timing of your interest. Do that for every payment and you have handed a third party a map of your financial life — the exact leak that running your own node was supposed to close. Pointing a self-hosted mempool.space instance at your own full node keeps those queries inside your own infrastructure. It is the explorer-shaped completion of the same principle behind running your own node and self-hosted Electrum servers.

What it shows

Beyond basic explorer functions, mempool.space excels at making fee dynamics legible. Its front page visualizes the unconfirmed-transaction backlog as a queue of candidate blocks, with fee-rate bands showing roughly what sat/vB is needed to confirm within one, three, or six blocks. For anyone timing a consolidation, opening a Lightning channel, or sweeping UTXOs during a low-fee window, this view is the practical tool. Miners and pool-watchers use it too: block pages show which mining pool found each block, template composition, and fee totals — data that feeds directly into the pool-decentralization conversation. Importantly, your node's mempool is your node's view; relay policy differs between nodes, so a self-hosted instance shows you what your node will relay and accept, which can differ from the public site's view.

Deployment paths

The project offers one-click installation on the major node platforms — Umbrel, RaspiBlitz, MyNode, RoninDojo, and StartOS — as well as manual and Docker deployments for operators running their own servers. The stack pairs the explorer with an Electrum-protocol backend (electrs or similar) over your node, so address lookups are served locally. Hardware demands are modest by node standards, though the address index adds meaningful disk usage on top of the chain itself.

Explorer, not oracle

For miners specifically, a self-hosted instance doubles as an operations dashboard. Watching the projected next block tells you what fee environment your own transactions face when consolidating payouts, and the block-by-block pool attribution makes pool luck and orphan events visible rather than anecdotal. If you run against your own Bitcoin Core node, the explorer also becomes a sanity-check tool during troubleshooting: when a payout seems missing, you can confirm within your own trust boundary whether the transaction was ever broadcast, whether it sits unconfirmed at too low a fee, or whether it confirmed to an address you mislabeled — all without typing your addresses into a stranger's website. The deployment cost of that capability is modest, and on platforms with one-click installs it is nearly free. Once it is running, most operators find the fee-visualization page becomes the tab they check before every on-chain action, the way a miner checks hashprice before flipping breakers.

A block explorer is a window, not a source of truth — your full node's validation is the truth. Treat any explorer, including your own, as a convenience layer over the node underneath. That framing keeps the trust model honest: the explorer helps you read the chain; the node is what verifies it. For the concepts it visualizes, see mempool and block header.