#beacon-chain

The live Ethereum validator entry and exit queues, read keyless straight from a public consensus-layer (Beacon) node. To stake on Ethereum you join a queue to activate a validator, and to unstake you join a separate queue to exit — both rate-limited by the protocol churn limit. The size of these queues is the cleanest real-time signal of staking demand and exit pressure: a long entry queue means capital is rushing in to stake, a long exit queue means validators are leaving. Liquid-staking protocols, exchanges, stakers and ETH analysts watch the queue to time deposits and withdrawals. The queue endpoint is the headline dashboard — how much ETH is waiting to activate (entry) versus exit, the validator counts behind each, the net flow, and an estimate of how long each queue takes to clear at the current activation/exit churn limit (256 ETH per epoch, ~6.4 min). The entry endpoint breaks down the activation side (validators already eligible and churning in, plus freshly-deposited validators not yet eligible). The exit endpoint breaks down the exit side (voluntary exits plus validators forced out by slashing). The validator endpoint looks up any single validator by index or public key: status, balance, effective balance, slashed flag and activation/exit epochs with wall-clock times. ETH amounts are the meaningful queue metric — a single post-Pectra validator can hold up to 2048 ETH — with counts given alongside. Distinct from beaconchain-api (consensus finality), the Solana validator feeds and the liquid-staking protocol feeds. Live, keyless, nothing stored beyond a short cache.

api.oanor.com/ethstakingqueue-api

The live consensus state of Ethereum's Beacon Chain — the proof-of-stake layer that secures Ethereum — read keyless straight from a public consensus-layer node. The single thing that matters for the health of proof-of-stake Ethereum is whether it is finalizing: every epoch (about every six and a half minutes) the validators are supposed to justify and then finalize the chain, and on the rare occasions that finality stalls — as it briefly did in 2023 — staking services, exchanges and bridges need to know immediately. The status endpoint returns the current head slot and epoch, how far through the current epoch the chain is and how long until the next one, the finalized and justified epochs, the finality lag (how many epochs behind finality the head is — a lag of two is healthy, a growing lag is trouble) and whether the node is fully synced and finalizing. The finality endpoint returns the finalized, current-justified and previous-justified checkpoints in detail, with how far behind the head each is in epochs and minutes. The genesis endpoint returns the chain's genesis time, how long Ethereum proof-of-stake has been running and the slot/epoch timing constants (a slot every 12 seconds, 32 slots per epoch). This is the Ethereum consensus / finality cut — distinct from the execution-layer feeds (gas, blocks, transactions), the staking-token and restaking feeds and the price feeds: it is the beacon chain's own heartbeat. Note it reports consensus state (slots, epochs, finality), not per-validator economics, which a public consensus node does not serve in one call. Times are UTC; epochs and slots are integers. No key, nothing stored beyond a short cache.

api.oanor.com/beaconchain-api