METHODOLOGY // HOW THE NUMBERS ARE MEASURED

How Ethereum Beat
measures network health

What is Ethereum network health?

Ethereum network health is a set of non-financial measures of how well the protocol is doing its job: whether the chain is producing and finalising blocks, how decentralised the nodes and validators are, how much it is used, and how much value it secures. Ethereum Beat surfaces one such measure per 12-second slot — no prices, no market talk.

How many Ethereum nodes are there, and where are they?

Ethereum runs on thousands of independently operated execution and consensus nodes spread across many countries. The Nodes channel shows the live count and the country distribution on a dot-matrix world map, plus client-diversity bars — geographic and client spread is what makes the network hard to censor or switch off.

Is Ethereum decentralised?

Decentralisation is measured, not assumed. Ethereum Beat tracks it directly: the number of independent nodes and the countries they run in, the diversity of consensus and execution clients (no single client should dominate), and the number of active validators securing the chain. Those figures are on the Nodes channel and in the individual metric pages.

What is Ethereum’s uptime?

The Ethereum mainnet has produced blocks continuously since genesis on 30 July 2015 — 100% uptime with no chain halts. Ethereum Beat counts the days of continuous uptime live from the genesis timestamp.

How fast does Ethereum finalise transactions?

Ethereum finalises in epochs of 32 twelve-second slots. A block is justified after one epoch and finalised after two, so finality trails the head of the chain by roughly 12.8 minutes under normal conditions. The Finality channel shows the current epoch filling slot by slot and the finalised checkpoint trailing behind the head.

What are blobs on Ethereum?

Blobs are the data-availability mechanism (EIP-4844) that lets Ethereum layer-2 rollups post their data cheaply to layer 1. Each block carries a number of blobs against a protocol target. The Blobs channel shows blob cells filling live per block, the blob base fee, and the daily blob count.

Where does Ethereum Beat get its data, and how is it collected?

Live per-slot values (block height, base fee, gas, blobs) come from public Ethereum RPC and Beacon endpoints, polled client-side once per slot. Daily series (activity, staking, value secured, blobs, node geography) come from open sources — growthepie (CC BY 4.0), the standard Beacon API, ultrasound.money, DefiLlama, ethernodes and public RPCs — collected once a day and stored in a small database. Every source is credited on the About page and in the footer, and the full time series is available from the open /api/snapshot and /api/metric endpoints.

Non-financial by design: no prices, no market cap, no trading. See the About page for every data source and licence, or the open /api/snapshot endpoint.