Home / Tools / Restore height

Monero restore height calculator

When you restore a wallet from its seed, Monero asks for a restore height: the block to start scanning from. Enter the date you created the wallet (or any date safely before your first payment) to get the block number to type in.

Chain tip: loading current height…

Quick pick
Recommended restore height
Copied

Better too early than too late

The restore height only decides where scanning starts, and the two ways to get it wrong aren't equal:

Too early → always safeYour wallet just scans some extra blocks. It takes a little longer to sync, but every coin is found. When unsure, go earlier.
Too late → missing fundsAny payment received before your restore height is skipped, so the wallet shows a wrong (low or zero) balance until you fix the height and rescan.

That's why this tool subtracts a 2-day safety buffer and rounds down — the same convention Monero's own wallets use.

Where to type this number

My restored wallet shows 0 (or too little) — how do I fix it?

Almost always the restore height was set too high, so earlier payments were skipped. You don't need to re-import your seed — just lower the height and rescan:

  • GUI: Settings → Info shows the restore height; set a lower one under Settings, then use "Rescan wallet balance".
  • CLI: run set_restore_height <lower number>, then rescan_bc.
  • Feather / Cake / Monerujo: Settings → rescan / "Rescan blockchain". If the height is locked in, re-create from seed with an earlier date.

When truly unsure, restore from genesis (height 1). It's slow but cannot miss anything.

How accurate is this, and where does the number come from?

The date↔height mapping is built from real block timestamps read straight from our own Monero node — 149 monthly checkpoints from the 2014 genesis to now — and interpolated between them (Monero targets one block every 2 minutes). That's the same checkpoint-table method the Feather wallet uses, and it's far more accurate than the flat "720 blocks/day since launch" estimate, which drifts by thousands of blocks over the years.

Block timestamps are set by miners and can wobble by up to two hours, so we treat the result as approximate and deliberately round down with a 2-day buffer. The math runs entirely in your browser, so the date you enter never leaves your device.