TheDocumentation Index
Fetch the complete documentation index at: https://docs.allium.so/llms.txt
Use this file to discover all available pages before exploring further.
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 throughstatus, activation_epoch, and exit_epoch fields to understand current validator lifecycle positions.
Table Columns
Search Optimization:validator_index
Unique Key: unique_id
| Column Name | Description |
|---|---|
| slot_number | Beacon Chain slot number |
| slot_timestamp | Beacon Chain slot timestamp |
| validator_index | The index of validator in validator registry |
| pubkey | The validator’s BLS public key, uniquely identifying them. 48-bytes, hex encoded with 0x prefix, case insensitive |
| balance | Balance of the validator in ETH |
| raw_balance | Raw balance of the validator in gwei (1e9 gwei = 1 ETH on Beacon Chain) |
| effective_balance | The 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_balance | The 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 |
| slashed | Boolean indicating if the validator has been slashed |
| status | Validator status (e.g., active_ongoing, withdrawal_done, exited_unslashed, exited_slashed, pending_queued, pending_initialized) |
| activation_eligibility_epoch | The epoch when the validator became eligible for activation |
| activation_epoch | The epoch when the validator was activated |
| exit_epoch | The epoch when the validator exited or will exit |
| withdrawable_epoch | The epoch when the validator’s balance becomes withdrawable |
| withdrawal_credentials | A 32-byte field associated with every validator, initially set during deposit, for verifying the destination of valid withdrawals |
| withdrawal_prefix | The BLS credentials (Type 0, or 0x00) or execution (Ethereum address) credentials (Type 1, or 0x01) |
| withdrawal_address | Withdrawal address of the validator (Ethereum address extracted from withdrawal credentials) |
| execution_optimistic | A boolean indicating whether the execution is done optimistically. If true, the response references an unverified execution payload that may be invalidated later |
| finalized | A boolean indicating whether the data has been finalized |
| unique_id | Unique ID constructed with validator_index and other identifying fields |
| _created_at | Timestamp of when the balance data was created in the database |
| _updated_at | Timestamp of when the balance data was last updated in the database |