block and head sound even cleaner than block_gossip. A block event says the beacon node saw a block. A head event says fork choice moved to it. If those rows show up hours after the slot started, the first question should not be "did Ethereum propagate blocks hours late?" It should be "what denominator did I just use?"
The denominator was the row.
block_gossip sounds like the clean block-arrival clock. Most of the time it is. Then Caplin shows up with canonical block roots arriving eight minutes after the slot started, which is not how blocks propagate on Ethereum unless something has gone very wrong.
Nothing went very wrong.
I expected finalized_checkpoint to be boring.
It has four useful fields: block, state, epoch, and execution_optimistic. The obvious read is that block is the finalized checkpoint block root and state is the finalized checkpoint state root.
For six clients, that is exactly what shows up.
For Lodestar and Grandine, it is not.
Attestations are not a smooth cloud of votes.
They pulse.
"Fast confirmation" sounds like something that should happen early.
On mainnet, at least in the one Xatu node emitting the new Beacon API event, it happens at 11.555 seconds into a 12-second slot.
That is fast compared with finality. It is not fast compared with the slot clock.
Correction, 2026-08-13: Ethereum did not lose finality on March 2. A non-
GLOBALjoin across distributed ClickHouse tables dropped canonical block matches and mislabelled ordinary slots as orphans. The corrected peak hourly orphan rate is 0.33%, minimum canonical participation is 99.10%, and every epoch in the window remained exactly two epochs behind finality. I retract the zero-participation, three-hour finality-loss, entity-wide-fork, and escalating-incident claims. The full correction reproduces the join bug and cross-checks raw checkpoints.
Something significant happened to Ethereum four days ago, and it's largely flown under the radar.
On March 2, 2026, between roughly 10:24 and 13:00 UTC, the mainnet experienced its most severe consensus disruption since the proof-of-stake transition. Block orphan rates hit 68%. Validator participation collapsed to zero in at least one epoch. The chain stopped finalizing — not for twenty minutes like the May 2023 incident, but for close to three hours.
This is the third network incident in twelve days.
Every MEV dashboard focuses on the same number: the execution layer bid that the winning builder pays the proposer. It's tracked obsessively. Tournaments are run around it. Entire firms exist to maximise it. And for 93% of blocks proposed on mainnet right now, it's the smaller of the two income streams the proposer receives.
The other stream — the consensus layer's attestation inclusion reward — sits quietly in the background, never shown on dashboards, never cited in "MEV revenue" charts. It's roughly four and a half times larger than the median MEV-boost payment.
Every attestation Ethereum's 960,000-odd validators cast has a clock on it. The slot it belongs to ticks past, and then proposers have up to 32 slots to pick it up and include it in a block. Include it in the very next slot and the attester earns a full reward. Wait two slots and the head-vote component — about three-sevenths of the total attestation reward — is already gone.
Most people assume this is a solved problem. Look at the median inclusion delay and you'd agree: it sits at roughly 1.001 slots and barely moves. The typical attestation is included almost immediately.
The median isn't the story.
Correction, 2026-08-13: The timing cliff in this post still reproduces, but the headline orphan total and both February "network split" sections were wrong. A non-
GLOBALjoin across distributed ClickHouse tables dropped canonical matches and mislabelled ordinary slots as orphans. Corrected peaks are 0.67% for both February windows, not 63% and 78%, and the corrected 30-day total is 390 unique orphan block roots, not 1,783. I retract the parallel-chain, self-healing-fork, entity-wide-incident, and 58%-of-month claims. The full correction reproduces the model bug and cross-checks finality.
Ethereum's block orphan rate should be nearly zero. It isn't — and the reasons why are more interesting than the number itself.
Over the last 30 days, 1,783 blocks were proposed on mainnet and then lost. Not missed (nobody tried), not reverted (execution failed) — proposed, gossiped, and then quietly discarded when another block won the fork choice. That's 59 blocks per day that disappeared into the void.
Most of them arrived on time.
Every 6.4 minutes, Ethereum's consensus clients have a problem. At the boundary between epochs, they need to do expensive work — update validator balances, compute committee assignments, tick the justification/finalization machinery. While they're doing it, the network doesn't stop. Blocks keep arriving. Attesters keep committing to what they see.
What happens to validators whose client is still mid-computation when the attestation window opens? They vote for the wrong head.