Entry Queue Latest

The beacon.validator.entry_queue_latest model provides the estimated epoch and timestamp where a pending deposit from Beacon Chain is expected to be processed. It provides the estimated entry timestamp and hours to entry for a given validator. The estimated entry timestamp and epoch is based on the current churn rate, beacon chain deposit index of the validator and the amount of ETH in front of the validator. The outputs of the model is expected to vary around +/- 1-2 epochs. This model is derived from beacon.validator.balances_latest and beacon.raw.pending_deposits, and is updated approximately every 30 minutes.

Schema

Column Name	Type	Description
epoch_number	bigint	Epoch number of the state where the pending deposits to beacon chain is fetched.
slot_number	bigint	Slot number of the state where the pending deposits to beacon chain is fetched.
slot_timestamp	timestamp	Slot timestamp of the state where the pending deposits to beacon chain is fetched.
deposit_index	bigint	(Nullable) Deposit index of the entry from the Execution Layer. This is based on the order of deposits from Execution Layer to Beacon Chain via EIP-6110. NULL when the pending deposit originates from consensus layer operations (e.g., validator consolidations via EIP-7251, or excess balance from exiting validators) rather than the execution layer deposit contract.
deposit_slot	bigint	The slot number where the deposit is made into beacon chain. When slot=0 (GENESIS_SLOT), this indicates the pending deposit did NOT originate from the Execution Layer - typically from validator consolidations (EIP-7251) or excess balance from exiting validators. These deposits are created by consensus layer operations and will have deposit_index=NULL.
pubkey	string	The validator’s BLS public key, uniquely identifying them. 48-bytes, hex encoded with 0x prefix, case insensitive.
validator_index	bigint	(Nullable) Unique index of the validator. Once a validator has been processed and added to the beacon state’s validators, the validator’s validator_index is defined by the index into the registry at which the ValidatorRecord contains the pubkey specified in the validator’s deposit.
status	string	(Nullable) Current status of the validator. Once a validator has been processed and added to the beacon state’s validators, the validator’s status is defined by the status of the ValidatorRecord in the beacon state.
exit_epoch	bigint	Epoch when validator exited.
eth_pending	numeric	Amount of ETH that is pending for deposits for the validator.
eth_in_queue	numeric	The total amount of ETH in front of the validator waiting to be processed for deposits.
epoch_to_entry	bigint	Estimated number of epochs to entry for deposits base on the current churn rate.
est_entry_epoch	bigint	Estimated entry epoch number where the deposit is expected to be processed.
est_entry_timestamp	timestamp	Estimated entry timestamp where the deposit is expected to be processed.
_pending_deposit_updated_at	timestamp	Timestamp of the entry update for pending deposits.
_balances_latest_updated_at	timestamp	Timestamp of the entry update for beacon state balances.

Example Query

The following query fetches the estimated entry timestamp and hours to entry for a given validator. Note that not all validators will have an index if they are not met the activation eligibility epoch.

SELECT
  pubkey,
  eth_pending,
  eth_in_queue,
  epoch_to_entry,
  est_entry_timestamp,
  datediff('hours', current_timestamp, est_entry_timestamp) as hours_to_entry
FROM beacon.validator.entry_queue_latest
WHERE pubkey in ('') -- Insert validator pubkey here

This query shows the top 5 validators with pending deposits, ordered by the amount of ETH in queue in front of them.

Overview

Data Verticals

Solana

Hyperliquid

Lighter

Bitcoin Ecosystem

EVM

Cosmos Ecosystem

Move Ecosystem

Other Ecosystems

Schema

Example Query

​Schema

​Example Query

Schema

Example Query