bitunix

Block Height

Vaihteluväli
  • 1M1M
  • 3M3M
  • 6M6M
  • 1Y1Y
  • ALLALL
Asteikko
  • LineaarinenLineaarinen
  • LogaritminenLogaritminen
Uusin
973.614K
2026-10-28 · 973,614 · lohkoa
1D-muutos
+0.01%
Edell. 973.47K
7D-muutos
+0.11%
Edell. 972.546K
30D-muutos
+0.47%
Edell. 969.069K
4Y-persentiili
100%
Koko historia 100%
Kaikkien aikojen huippu
973.614K
2026-10-28 · 0.00%
1Y-vaihteluväli
921.259K – 973.614K
Alkaen 2009-01-03
Ladataan dataa…

Tietoa tästä mittarista

Mitä se mittaa

Block Height is the sequential position of the latest block in the chain at each daily observation, measured in blocks above the genesis block. Genesis has height 0, so a chain whose tip has height h contains h + 1 blocks including genesis.

Näin luet sitä

The line advances as blocks are added; its daily increase describes chain progress, not a growth rate in users or capital. Halvings occur at multiples of 210,000 blocks, and the April 20, 2024 daily reading was 840,128, already past that halving’s trigger at height 840,000.

Rising height and fresh all-time highs are normal consequences of an extending chain, not evidence of stronger valuation. The chart is a daily history rather than a live block explorer; short reorganizations and observation boundaries can affect how individual increments compare with daily block counts.

Tiheys
Päivittäin (UTC 00:00)
Omaisuuserä
BTC
Tyyppi
Yksittäinen arvo
Yksikkö
lohkoa
Dataa alkaen
2009-01-03
Uusin data
2026-10-28
Datapisteet
6,508

UKK

Why does Bitcoin block height start at zero?

The genesis block is assigned height 0. Height counts the steps above genesis, so total blocks including genesis is one more than the tip’s height.

At which block heights do Bitcoin halvings happen?

The subsidy halves every 210,000 blocks. The first four trigger heights were 210,000, 420,000, 630,000 and 840,000; a daily chart can show a later height on those dates.

Can block height give an exact date for the next halving?

It identifies how many blocks remain until the trigger height. Converting that distance to a calendar date requires an assumed block pace, so the date remains an estimate.