multichain
/index /tools /25 bitcoin-block-date
live

Block height
↔ date.

Tip
959,681
estimated (API offline)
Target
10 min
per block, long-run
History
Anchored
genesis + halvings
Auth
None
no wallet, no API key
/25BLOCK HEIGHT ↔ DATE
offline est.
block height
0 → future
date
UTC

/notes

01
How the estimate works.
Past heights interpolate between documented moments: genesis, two early-era waypoints, and every halving, then the live tip. Future heights extrapolate from the tip at the 10-minute target. No header database, no API key.
02
Why the early years need anchors.
2009 blocks arrived far slower than target because difficulty could not fall below 1 while almost nobody mined. A flat 10-minute average from genesis would misdate early blocks by months; the waypoints keep the whole timeline within days.
03
Halvings are heights, not dates.
The subsidy halves every 210,000 blocks, so every halving date you have ever seen was an estimate exactly like this one. The halving countdown tracks the next one against the live tip.

/faq

01

How accurate are the estimates?

Future dates assume the 10-minute target, so they drift as hashrate changes and tighten as the block approaches; a year out, expect give-or-take a couple of weeks. Past dates interpolate between documented moments (genesis, early waypoints, every halving) and land within days for most of history.

02

When will block 1,000,000 be mined?

Type 1,000,000 above and the tool computes it from the live tip at the 10-minute target. The estimate sharpens continuously; check back as the height approaches.

03

Why not show the exact timestamp for past blocks?

Exact historical timestamps live in the blockchain itself and any block explorer will show them. This tool answers the direction explorers are bad at, dates from heights and heights from dates, without an API key, so it estimates instead of indexing 900,000+ headers.

04

Why do block timestamps jitter anyway?

Miners set timestamps themselves within consensus tolerance (roughly two hours), and the difficulty adjustment only re-targets every 2,016 blocks. Ten minutes is the long-run average, not a metronome; individual gaps of seconds or over an hour are routine.