Skip to content
Bitcoin Beat Proof of Work, LiveOpen live experience ↗

Where Bitcoin Beat gets its live data

Updated · Bitcoin Beat

The public Bitcoin Beat site receives Bitcoin network observations directly in the visitor’s browser from public mempool instances. Exchange quotes arrive through a separate public market-data connection. The website itself is statically hosted.

Blocks, transactions and mining information

The primary source is mempool.space. WebSocket messages supply the recent chain, mempool statistics and a projected next block; public API requests provide additional block information. The projection belongs to that observer. Different miners can build different candidate blocks.

If the primary source does not provide usable data, the application can try mempool.emzy.de, mempool.ninja and mempool.bullbitcoin.com, in that order. These are public instances of the same open-source explorer software. Availability and update cadence can differ, and a different hostname does not guarantee independent infrastructure. The application checks whether a source’s chain looks like Bitcoin before using it.

Where does the price come from?

The preferred quote is Binance’s BTC/USDT latest trade. If unavailable, the browser tries Coinbase BTC-USD, then Kraken BTC/USD, and finally the data provider’s price. USDT is a dollar-linked token, not US dollars; the live interface displays the preferred quote using its existing dollar notation. Hover over the price in the live view to read the current provider and market.

Exchange updates and the chain data are separate streams. A quote can change without a new block, and a network snapshot can arrive without a new trade.

What does “live” guarantee?

Live means the page responds to observations received during this visit. It does not guarantee zero delay, full network coverage or uninterrupted access. Internet conditions, upstream processing and browser scheduling affect arrival time. A block-header timestamp is set by a miner and is not the exact moment your browser learned of that block.

The heartbeat line spreads newly observed transactions across the reporting interval, so it is deliberately one reporting batch behind. A real block’s arrival drives the large flash directly. Pool names and estimates depend on the provider’s available labels; a missing label is not fabricated.

Inspect the upstream interfaces

The mempool API documentation describes the public interfaces, and the mempool source repository documents the explorer implementation. For product controls and browser requirements, see questions and controls.