An Ethereum beacon chain explorer shows the consensus side of the network: the validators that propose and vote on blocks, the slots and epochs they work in, and the rewards, penalties and withdrawals that flow from it. A normal explorer such as Etherscan is built around transactions and addresses. A beacon explorer is built around validator indexes and duties. If you stake, run a node, or just want to know why your staking provider's rewards dipped last Tuesday, this is the tool you need.
People still search for an "Ethereum 2.0 explorer" or an "Ethereum PoS explorer". Same thing. Below we explain what the beacon chain is, how to read every field on a validator page under the rules that apply after the Pectra upgrade, and which explorers are worth your time in 2026.
898,537
Active validators
Finalized beacon state, queried by us from a public node on 24 Sep 2026
≈43.45M ETH
Effective balance at stake
Sum of effective balances of those active validators
22,874
Compounding (0x02) validators
Validators that opted into the Pectra 2,048 ETH cap
What the beacon chain is, and why "Ethereum 2.0" disappeared
The beacon chain went live on 1 December 2020 at 12:00:23 UTC. For almost two years it ran next to the original proof-of-work chain, producing empty blocks and letting validators practise consensus with real stakes but no real transactions. On 15 September 2022, the Merge joined the two. The last proof-of-work block was 15,537,393; the first proof-of-stake block, 15,537,394, landed in beacon slot 4,700,013. Since then, every Ethereum block is proposed by a validator chosen by the beacon chain.
The Ethereum Foundation dropped the "Eth2" and "Ethereum 2.0" labels in early 2022 in favour of "execution layer" (transactions, accounts, the EVM) and "consensus layer" (validators, the beacon chain). The old name hangs on in search queries and in some explorer branding, but there is no separate Ethereum 2 network to explore. You explore one chain from two angles. The proof-of-stake documentation on ethereum.org is the best primer if you want the full protocol picture.
Slots, epochs and finality on a beacon explorer
Time on the beacon chain is cut into slots of 12 seconds. Each slot has exactly one validator selected to propose a block. If that validator is offline, the slot is missed and the chain simply waits for the next one, which is why a beacon explorer shows gaps and "missed" badges while a normal explorer just shows a slightly longer block time. Thirty-two slots make an epoch, roughly 6.4 minutes. Within each epoch, every active validator is assigned to attest (vote) once.
Finality works on epoch boundaries. When two-thirds of the staked ETH votes for a checkpoint, it becomes justified; when the next checkpoint is justified on top of it, the earlier one is finalized. In normal conditions that takes about two epochs, or 12.8 minutes. Beacon explorers show the latest justified and finalized epochs on their front page. If those numbers stop moving, the network has a problem and you will hear about it quickly.
Slot numbers are also a handy way to line up execution and consensus data. Our live Ethereum explorer shows the slot and epoch for every block and transaction it displays, computed from the block timestamp minus the genesis time, divided by 12. So a block with a timestamp on 24 September 2026 lands somewhere past slot 15.28 million, epoch 477,000-something. Copy the slot number into a beacon explorer and you see who proposed it, whether it carried MEV payments and how many attestations it included.
Reading a validator page, field by field
Search a beacon chain explorer for a validator index, a public key or a deposit address, and you land on a validator page. Here is what each part means.
Index and public key
The public key is a 48-byte BLS key (96 hex characters) created when the validator's keys were generated. The index is the number the beacon chain assigns when the deposit is processed, starting at 0 in 2020 and now past two million, since indexes are never reused even after a validator exits. Explorers accept either. The index is far easier to share, so most dashboards and monitoring tools use it.
Balance and effective balance
The balance is the exact amount of ETH the validator holds on the consensus layer, updated every epoch as rewards and penalties land. The effective balance is what the protocol uses to weigh votes and calculate rewards. It is a whole number of ETH that only changes when the real balance moves past a buffer, so it does not flicker every few minutes.
Until May 2025 the cap was 32 ETH. The Pectra upgrade on 7 May 2025 brought EIP-7251, which lets validators with the new 0x02 "compounding" credentials hold an effective balance of up to 2,048 ETH. Rewards above 32 ETH now keep earning instead of being skimmed off, and large operators can consolidate many 32 ETH validators into one. When we sampled the validator set in September 2026, 14,124 active validators already had an effective balance above 32 ETH. On an explorer you will see this as a consolidation event in the validator's history and a much larger balance chart.
Attestations
Every epoch, each validator should cast one attestation voting for the chain head, the source and the target checkpoint. A beacon explorer lists them with the slot they were included in and the inclusion delay. Missed attestations cost a small penalty, roughly the reward you would have earned. A handful per week is normal (a restart, a brief network hiccup). A long streak means your node is down or out of sync. This is the first place to look when rewards drop.
Proposals
Block proposals are rare and valuable. With around 900,000 active validators and one proposer per slot, an individual 32 ETH validator proposes only a few blocks per year on average; larger compounding validators are picked proportionally more often. The explorer shows each proposed or missed slot, the execution block number, the fee recipient and, on explorers that track MEV-Boost relays, which relay delivered the block and what it paid. Priority fees and MEV go to the fee recipient address on the execution layer, which is why you will also see them in that address's history on a regular explorer.
Sync committee duties
A random set of 512 validators forms the sync committee for 256 epochs, about 27 hours. Members sign every block head so that light clients can follow the chain cheaply. Being selected is uncommon and pays well; missing those signatures costs correspondingly more. Explorers list the committee periods a validator has served in and its participation rate.
Status
Validators move through a lifecycle: pending (deposit seen, waiting in the activation queue), active_ongoing, active_exiting (exit requested), exited, and finally withdrawal_done once the balance has been swept out. An active_slashed or exited_slashed label means the validator broke a slashing rule. Explorers also show the activation and exit queues, which can stretch from hours to weeks depending on demand.
Withdrawals and withdrawal credentials: 0x00, 0x01 and 0x02
Withdrawal credentials decide where a validator's ETH can go. Explorers display them in the validator's details, and the first byte tells you a lot:
- 0x00 means BLS credentials from the early days. These validators cannot withdraw until the owner signs a one-time change to an execution address. In our September 2026 sample, 8,917 active validators still had them.
- 0x01 points at an execution-layer address. Anything above 32 ETH is skimmed there automatically, and a full exit sends the whole balance. This is still the vast majority.
- 0x02, added in Pectra, also points at an execution address but compounds rewards up to 2,048 ETH before skimming.
Withdrawals themselves are not transactions. Since the Shapella upgrade on 12 April 2023, the protocol sweeps through validators in index order and credits up to 16 withdrawals per block directly to the target addresses. That is why a withdrawal shows up on Etherscan or Blockscout under a separate "Withdrawals" tab, not in the transaction list, with a withdrawal index (by September 2026 Blockscout's counter was past 144 million) and the validator index it came from. Pectra also added execution-layer triggered exits (EIP-7002), so a withdrawal address can now request an exit without the validator's signing key, which matters a lot for staking pools.
If you are checking whether a withdrawal reached your wallet, look at the receiving address in an execution explorer. Our Ethereum address explorer guide shows where withdrawals appear and why they do not count toward the transaction total.
Slashing: what it is and how an explorer shows it
Slashing punishes provable attacks rather than downtime. There are three offences: proposing two different blocks for the same slot, casting two different attestations for the same target, and casting an attestation that "surrounds" an earlier one. Almost every real-world slashing has been an operator accident, usually running the same keys on two machines during a migration.
The consequences come in stages. An immediate penalty is taken and the validator is forced to exit. After Pectra, that initial penalty is 1/4,096 of the effective balance, far smaller than the old 1/32. Around 18 days into the roughly 36-day exit period, a correlation penalty is applied that scales with how much other stake was slashed around the same time. One isolated mistake stays cheap; a mass slashing from a shared bug can be devastating. The validator also keeps losing attestation rewards until it exits.
Explorers flag slashed validators in red, show which validator reported the offence (the whistleblower gets a small reward) and list recent slashings on a dedicated page. The same check is worth doing on a staking provider before you delegate to them.
Beacon chain explorers compared
There are fewer beacon explorers than execution explorers, and they differ more. Here is how the main options stack up in September 2026.