Free online tools to generate, calculate,
convert, format, encode, and play.
 

Unix Timestamp / Block Estimator

Estimate which blockchain block number corresponds to a given Unix timestamp, or convert a block number back to an approximate timestamp. Supports Bitcoin, Ethereum, Solana, Base, and Arbitrum.


Blockchain

Convert

Seconds since Jan 1, 1970 00:00:00 UTC
The estimate updates as you type.

Quick Examples


How It Works

Each blockchain produces blocks at a roughly predictable rate. By knowing the genesis timestamp (when block 0 was mined) and the average block time, we can estimate the relationship between Unix timestamps and block numbers.

Estimated Block = (Timestamp − Genesis Timestamp) ÷ Average Block Time

Estimated Timestamp = Genesis Timestamp + (Block Number × Average Block Time)

Chain Parameters

Chain Genesis Timestamp Avg Block Time Notes
Bitcoin 1231006505 ~600s (10 min) Difficulty adjusts every 2016 blocks
Ethereum (pre-Merge) 1438269973 ~13.3s Proof of Work era (blocks 0 – 15,537,393)
Ethereum (post-Merge) — 12s exactly Proof of Stake since Sep 15, 2022
Solana 1584316800 ~0.4s (400ms) Uses slots; times vary with network load
Base 1686789347 2s Optimism-based L2; blocks every 2 seconds
Arbitrum One 1622243344 ~0.26s (260ms) L2 blocks produced on-demand by sequencer

Accuracy Considerations

  • Bitcoin — Block times vary significantly (1 min to 60+ min) depending on difficulty and hash rate. The 10-minute average holds well over long periods but individual blocks can be far off.
  • Ethereum (PoW) — Pre-Merge block times averaged ~13.3s but varied with network congestion and difficulty bombs.
  • Ethereum (PoS) — Post-Merge blocks are produced every 12 seconds with high regularity, making estimates more accurate. Occasionally slots are missed, adding minor variance.
  • Solana — Slot times average ~400ms but vary with network congestion and validator performance. Slots can also be skipped, adding gaps in the sequence.
  • Base — As an Optimism-based L2, blocks are produced every 2 seconds by the sequencer. Sequencer downtime can cause gaps.
  • Arbitrum — Blocks are produced on-demand by the sequencer at ~0.26s average, but timing is highly variable and depends on transaction activity.
  • General — Estimates are more accurate for dates closer to the present. For historical dates, checking a block explorer is recommended for exact results.

Embed This Util

You can embed this util on your own site as a widget. Adding ?embed=1 to the URL loads a compact version with just the tool itself; no header, menu, or documentation. Paste this snippet into your HTML:


    

Copy snippet Adjust the height to taste.



Feedback

Help us improve this page by providing feedback, and include your name/email if you want us to reach back. Thank you in advance.


Share with