Bitcoin network activity and security
Activity, security and supply: Bitcoin observed directly on the network.
Supply & next halving
Protocol rules · not a price forecastNext halving
ESTIMATED DATE · UNCERTAINWaiting for block data
This is an estimate calculated now, not a protocol deadline. It can move earlier or later as block times and network conditions change.
The estimate is recalculated during automatic network-data updates. Future difficulty and block times cannot be predicted.
Every 210,000 blocks, new issuance is halved. The time between blocks varies: the future date is uncertain.
Cost of a transaction
PendingSize depends on inputs, outputs and address type. Waiting times are not guaranteed.
On-chain indicators
CoinMetrics Community · observation pendingMetrics not included in the public plan are shown as —. Values refer to the date indicated by the source, even when the site has just been refreshed.
Mining & security
Estimates from mempool.spaceThe activity behind the price
Latest 31 available daily observations · Coin Metrics Community
Daily series, not intraday. Missing points are not interpolated. Exchange flows cover addresses attributed by the provider; an internal transfer may not correspond to a purchase or sale.
Valuation & exchange supply
Coin Metrics inputs from the same daily observation · Date unavailable
Realized capitalization / supply
1 − 1/MVRV · not entity-adjusted
Addresses identified by the provider
On-chain inflows minus outflows
Exchange supply is not complete proof of reserves and does not include operators' liabilities. Realized price and NUPL are transparent calculations from daily data: they do not use the current spot price or identify individual investors.
Shares of observed blocks, not a direct measure of hashrate or individual miners' control. Pool attribution depends on the provider.
The latest blocks
The network continues. One block at a time.
| Height | Time · Rome | Pool | Transactions | Size | Total fees |
|---|
Total block fees excluding new issuance. Size is in decimal MB; the protocol limit is expressed in weight, not in byte size alone.
How to read these data
Network data is checked every minute. The next halving date is estimated from the observed block and the recent difficulty-adjusted average block interval under mempool.space’s model. When unavailable, the ten-minute-per-block assumption is stated. The date can change: the protocol fixes a block height, not a calendar day.
Coin Metrics Community metrics are daily observations, even when the site has just requested them. MVRV, NUPL and realized price retain the date and methodology of their inputs. Active addresses are not people, and exchange flows cover addresses identified by the provider rather than every operator.