Today's block 19,438,201 — a daily companion for the curious.
The chain, right now.
Three live signals — gas, throughput, and the validators keeping the lights on. Pulled from a thin WebSocket proxy, throttled to one paint per frame.
Today's idea: What is a reorg?
A short explainer, refreshed daily. The chain is a tree pretending to be a line — and reorgs are when the lie briefly breaks.
A reorg — short for reorganization — happens when the network briefly disagrees on which block is canonical. Two miners produce blocks at nearly the same height. Both propagate. Half the network sees one first; half sees the other.
For a moment, two parallel histories exist. Then the next block lands on top of one of them, and the other is orphaned. The orphaned block's transactions slide back into the mempool. Most users never notice — but if you watched closely, the chain just held its breath.
The chart on the right shows the past 30 days. Each spike is a reorg event; each spike's height is its depth in blocks. Most are 1-deep — a hiccup. Anything past 3 deep is worth a phone call.
- 01 One-deep reorgs are normal — under load they happen ~hourly.
- 02 Two-deep is rare; three-deep is news.
- 03 Finality kicks in after 64 slots — past that, the chain forgets how to forget.
A small toolbelt.
Four utilities that earn their place. Open one, get an answer, close the tab.
Address Lookup
Resolve any 0x… or ENS name to its on-chain identity. Balance, first seen, label.
Open 02Gas Estimator
Pick a transaction type, get the median fee for the next ten blocks at three confidence levels.
Open 03Block Explorer
Drop a block height or transaction hash; we return a readable, annotated breakdown.
Open 04Daily RSS
One short, opinionated post per day in your reader. Plain text, footnoted, never a newsletter.
SubscribeThe ledger.
Every previous day, in order. A literal record — no algorithm, no surfacing, no scoring. Click a row to read.