Live protocol data
Bitcoin Network
Chain tip, block cadence, difficulty epoch progress, fee pressure and the pending transaction queue.
Chain state
Where the chain stands.
Confirmed block height
—
Last block found —
Observed block interval
—
Target 10m 00s · deviation —
Pending transactions
—
— waiting · — congestion
Queue depth
—
Blocks needed to clear the mempool at current size
Difficulty epoch
Bitcoin’s self-correcting clock.
Every 2,016 blocks the network measures how long those blocks actually took and adjusts difficulty so the next 2,016 land closer to two weeks. This is that measurement, in progress.
Epoch progress—Of 2,016 blocks
Blocks remaining—Until block —
Projected change—Estimated —
Previous retarget—The last completed adjustment
Projections extrapolate the observed block interval across the remaining epoch and are clamped to Bitcoin’s ×4 retarget limit. Early in an epoch they are drawn from very few blocks. Full difficulty detail.
Next block
What the network is about to confirm.
Projected next block
- Fee range
- —
- Transactions
- —
Derived from the current mempool as miners would order it by fee rate. It changes as transactions arrive, confirm or replace themselves.
Most recent block
- Size
- —
- Weight used
- —
- Median fee rate
- —
- Fee share of reward
Recent blocks
The last ten blocks found.
| Height | Found | Transactions | Fees | Pool |
|---|---|---|---|---|
| Loading blocks… | ||||
Go deeper
Follow the thread.
NetworkMempoolQueue depth, fee-rate distribution and the blocks it would produce.
NetworkFeesWhat confirmation costs right now, in sats and dollars.
MiningHashrateThe security spend behind every block, with historical context.
NetworkLightningPublic channel graph capacity, nodes and growth.
MonetarySupplyExact issuance against the 21 million cap.
NetworkOn-chain activitySampled large transfers from recently confirmed blocks.