Skip to main content

​
🦸 Summary view

The summary table is part of the validator dashboard. It provides detailed performance metrics for each validator group, including BeaconScore® and validator rewards across various time frames. It also features a historical chart view.

​
Overview

Each row in the summary table represents a validator group. Users with multiple groups will see an additional row at the top, labeled as the Σ-row.

​
Expandable rows

Expanding a row provides detailed data for each group.

​
Absolute vs relative values

The summary table can be viewed in both absolute and relative values. This feature is especially useful for large entities with millions of attestations that prefer a relative value.
  1. Summary table with relative values

Summary table with relative values

  1. Summary table with absolute values

Summary table with absolute values

​
Missed Rewards Calculation

When a validator misses rewards — whether from the Consensus Layer (CL) or Execution Layer (EL) proposals, including MEV — those missed rewards are calculated using the median (p50) of the surrounding rewards. Specifically:
  1. Identify the Surrounding Slots
    • For each missed slot, consider the 32 slots surrounding it: slots where slot >= missed.slot - 16 AND slot < missed.slot + 16
  2. Calculate the Median (p50)
    • Collect the rewards from each of those surrounding 32 slots.
    • Compute the median (50th percentile, or p50) of that set of rewards.
  3. Assign the Median as the Missed Reward
    • The resulting median value becomes the missed reward for that specific slot.

​
Example

  • Suppose a missed proposal occurred at slot 100.
    • Look at slots 84 through 115 (i.e., 100 - 16 to 100 + 15).
    • Gather each validator’s reward (MEV rewards + CL rewards) from those slots.
    • Sort these rewards and take the median value.
    • The median is then recorded as the missed reward for slot 100.

​
APR calculation

The APR is calculated based on the growth rate of your consensus layer (CL) staking balance over the selected period, using epoch-level granularity. For every epoch in the period, the CL balance of each validator at the start of that epoch is recorded. The total rewards earned during the period are divided by the sum of these epoch starting balances, which gives the average growth rate per epoch. This rate is then annualized by scaling it to one year. APR = (RewardsInPeriod / SumOfEpochStartBalances) * EpochsPerYear * 100
  • SumOfEpochStartBalances: The CL balances of all validators at the start of each epoch, added up over every epoch in the period.
  • RewardsInPeriod: Total rewards accrued by those validators during the period.
  • EpochsPerYear: Number of epochs in a year of 365.25 days (≈82,181, each epoch is ~6.4 minutes).
The APR shown also includes the execution layer (EL) rewards of your proposed blocks, annualized the same way.

​
Luck calculation

Validators are randomly selected for duties, such as proposing blocks or participating in the sync committee. The chance of being assigned duties depends on the total number of validators on the network and their effective balance.
Luck values are purely informative and cannot be actively influenced.
Blocks
  1. It is calculated how likely a validator was to be chosen to propose a block in each epoch.
  1. The number of block proposals assigned to a validator, including missed ones, is measured against the expected number, expressed as a percentage.
In practice, this calculation is performed for all validators over the selected time frame. Sync Committee
  1. It is calculated how likely it was for a validator to be chosen as a member of the sync committee in each election.
  1. The number of actual participations is compared to the expected participations and expressed as a percentage.
In practice, this calculation is performed for all validators over the selected time frame.

​
Summary chart view

[1] View the historical performance of your validator groups by clicking this button and switching to the summary chart view.
[2] The summary chart view is perfect for debugging issues, as it provides historical performance data with epoch-level granularity. The Groups dropdown lets users filter specific groups, while the Total line (orange line) shows the average performance of all groups in the dashboard.

To identify missed blocks, sync duties, or attestations, users can use the Efficiency dropdown to filter for those specific duties.

​
Status column

The status column offers a quick way to check key duties, such as your current sync committees, whether you’re part of the upcoming sync committee, and if any of your validators have been slashed.

Hover over the icons for more details.

​
Validator column

The validator column displays the state of each validator in each group:
  • Online validators (green icon)
  • Offline validators (red icon)
  • Exited validators (gray icon)
A comma-separated list of validator indices for each group can be found in the popout modal for each row in the table.

Validator states

Validators state in relative values

The relative value only accounts for online and offline validators, ignoring those that have already exited the chain. This offers quick insights into whether your group is experiencing issues.

Popout modal with comma separated validator indices

​
BeaconScore®

The BeaconScore® metric is a comprehensive measure of validator performance, combining multiple components:
  • Red arrow: Below the network average.
  • Green arrow: Above the network average.
  • Yellow arrow: Equal to the network average.
Hovering over an arrow shows the network average the group is compared with. For historical performance, switch to the summary chart view.

​
Attestations vs Attester efficiency

  • Attester Efficiency: This measures how much reward a validator could have earned for attestations versus how much they actually earned. For example, if a validator could have earned 100 GWEI for attestations but only received 98 GWEI, the attester efficiency would be 98%.
  • Attestations (%-value): This represents the percentage of attestations successfully included in the network. For instance, if a validator managed to include 99 out of 100 attestations, the Attestation (%) value would be 99%.
The absolute values can be viewed by hovering over this percentage or by switching to the absolute-table view.