Skip to main content
The beacon.raw.balances_latest table provides the latest validator balances of all validators on the Beacon Chain. Each row represents a validator’s current balance state, including effective balance and validator status information. This table is updated every epoch and only includes finalized data.

​
Use Cases: Real-Time Monitoring & Analysis

This table is essential for real-time validator monitoring and current state analysis: Real-Time Monitoring: Track current validator balances and status to monitor active validators, detect recent slashing events, and observe ongoing validator operations. Use this table for live dashboards and alerting systems. Current State Analysis: Query the latest state of validators to understand current network composition, active stake distribution, and validator health. Identify validators by their withdrawal addresses or public keys for operational monitoring. Queue & Status Tracking: Monitor validator activation and exit status through status, activation_epoch, and exit_epoch fields to understand current validator lifecycle positions.

​
Table Columns

Search Optimization: validator_index Unique Key: unique_id
Column NameDescription
slot_numberBeacon Chain slot number
slot_timestampBeacon Chain slot timestamp
validator_indexThe index of validator in validator registry
pubkeyThe validator’s BLS public key, uniquely identifying them. 48-bytes, hex encoded with 0x prefix, case insensitive
balanceBalance of the validator in ETH
raw_balanceRaw balance of the validator in gwei (1e9 gwei = 1 ETH on Beacon Chain)
effective_balanceThe balance at stake in ETH. Effective balance is derived from the validator’s actual balance and prior effective balance, and is used to calculate the size of rewards and penalties
raw_effective_balanceThe balance at stake in gwei. Effective balance is derived from the validator’s actual balance and prior effective balance, and is used to calculate the size of rewards and penalties
slashedBoolean indicating if the validator has been slashed
statusValidator status (e.g., active_ongoing, withdrawal_done, exited_unslashed, exited_slashed, pending_queued, pending_initialized)
activation_eligibility_epochThe epoch when the validator became eligible for activation
activation_epochThe epoch when the validator was activated
exit_epochThe epoch when the validator exited or will exit
withdrawable_epochThe epoch when the validator’s balance becomes withdrawable
withdrawal_credentialsA 32-byte field associated with every validator, initially set during deposit, for verifying the destination of valid withdrawals
withdrawal_prefixThe BLS credentials (Type 0, or 0x00) or execution (Ethereum address) credentials (Type 1, or 0x01)
withdrawal_addressWithdrawal address of the validator (Ethereum address extracted from withdrawal credentials)
execution_optimisticA boolean indicating whether the execution is done optimistically. If true, the response references an unverified execution payload that may be invalidated later
finalizedA boolean indicating whether the data has been finalized
unique_idUnique ID constructed with validator_index and other identifying fields
_created_atTimestamp of when the balance data was created in the database
_updated_atTimestamp of when the balance data was last updated in the database

​
Sample Queries

​
Query 1: Get Latest Balances for All Active Validators

select 
    validator_index,
    balance,
    effective_balance,
    status,
    slot_timestamp
from beacon.raw.balances_latest
where status = 'active_ongoing'
order by validator_index

​
Query 2: Query Latest Balance for Specific Validators

select 
    *
from beacon.raw.balances_latest
where validator_index in (1, 1000, 145, 1589823)