Every full Ethereum node is currently lugging around 296 GB of state. Every account, every contract, every storage slot. Sync a fresh node and you're downloading all of it. Run a node continuously and you're holding all of it in your database, forever.

The uncomfortable truth: the vast majority of that state is dead. It hasn't moved in over a year. The addresses are abandoned, the contracts are deprecated, the protocols are gone. The data just... sits there. In every node on the network.

Ethereum's block gas limit doubled in 2025. Not through a hard fork. Not through a governance vote. Through three coordinated waves of validators updating their configuration files.

The limit went from 30 million to 60 million gas—a 100% increase in block capacity—between February and November 2025. Each wave moved faster than the last. The final surge, from 45M to 60M, took just 22 hours.

Ethereum had 660 chain reorganizations in the last 30 days. That's a 0.31% reorg rate across roughly 216,000 slots — normal background noise for a live PoS network.

But here's something nobody talks about: if you ask Lighthouse how deep those reorgs were, you'll get a completely different answer than if you ask Prysm. Same event. Same block hashes. Different depth. Every single time.

One validator missing an attestation isn't a crisis. A few hundred validators missing 1 in 8 attestations, every slot, for three months straight — that's a different story. And it's concentrated in a way that the aggregate participation numbers don't show.

The xatu dataset tracks missed attestations at the entity level. When you sort by miss rate, a clear hierarchy emerges — and a handful of operators sit far outside the expected range.

There's a counterintuitive pattern buried in Ethereum's block-building data: the most valuable blocks — the ones where MEV extractors collect the most ETH — consistently contain fewer transactions than ordinary blocks.

Not slightly fewer. Significantly fewer.

A block worth 0.2–1 ETH in MEV carries, on average, 185 transactions. A normal low-MEV block carries 293. That's 108 fewer transactions — a 37% drop from peak — in a block that everyone in the market fought hardest to produce.

One month after Pectra went live, roughly 44% of all Nethermind validator nodes are rejecting a blob retrieval call that was introduced in that very fork. Every other major execution client has mostly fixed this. Nethermind hasn't moved.

This is the data on what's happening, why it matters, and where the fault line sits.

Most validators proposing a block right now will earn about 0.011 ETH. That's the median. But the mean is 0.050 ETH — more than 4× higher. The reason the mean is so detached from the median tells you everything about how staking rewards actually work.

Over the 30 days ending February 26, 2026, there were 200,963 MEV-Boost blocks on mainnet. I deduped them by taking the highest bid per slot across all relays. Here's what I found.

Each blob on Ethereum costs the same regardless of how much data you actually put inside it. The slot doesn't know if you packed all 131,072 bytes or left 99% empty. You pay either way.

That flat pricing creates a question that hasn't been answered cleanly: how efficiently are rollups actually using the space they're buying? The answer turns out to span an enormous range — from 100% fill all the way down to a rollup that's posting the same completely empty blob, over and over, every block.

Something unusual happened on February 21, 2026. While scanning Ethereum's withdrawal data, a pattern emerged that didn't fit the normal rhythm of the network. 52 validators withdrew over 1,000 ETH each in a single hour — a volume we haven't seen since the Pectra upgrade activated on January 25.

When people talk about the Ethereum Virtual Machine, they reach for the "world computer" metaphor — a globally shared processor executing smart contract code. That framing implies computation: arithmetic, cryptography, logic. In practice, the EVM spends more than half its gas budget on something far more mundane: reading and writing persistent state.

Every week, roughly 1,440 gigagas of EVM execution passes through the mainnet. More than half — 56.7% — goes to exactly two opcodes.