Introduction
V1 API Docs
curl --request POST \
--url https://beaconcha.in/api/v2/ethereum/validators/performance-aggregate \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"validator": {
"validator_identifiers": [
1
]
},
"range": {
"evaluation_window": "24h"
},
"chain": "mainnet"
}
'{
"data": {
"beaconscore": {
"total": 0.5,
"attestation": 0.5,
"proposal": 0.5,
"sync_committee": 0.5
},
"duties": {
"attestation": {
"included": 123,
"assigned": 123,
"correct_head": 123,
"correct_source": 123,
"correct_target": 123,
"valuable_correct_head": 123,
"valuable_correct_source": 123,
"valuable_correct_target": 123,
"avg_inclusion_delay": 1.2,
"avg_inclusion_delay_excluding_missed_slots": 1.2,
"missed": 123
},
"sync_committee": {
"successful": 1,
"assigned": 1,
"missed": 1
},
"proposal": {
"successful": 123,
"assigned": 123,
"missed": 123,
"included_slashings": 123
}
},
"finality": "not_finalized"
},
"range": {
"slot": {
"start": 1,
"end": 1
},
"epoch": {
"start": 1,
"end": 1
},
"timestamp": {
"start": 1,
"end": 1
}
}
}Performance Aggregated
Returns aggregated performance metrics for a known collection or group of validators. Known collections are referenced by index, public key, deposit address, or withdrawal address.
This endpoint includes the BeaconScore (Validator Efficiency) metric, which measures how well validators perform their duties. Learn more about how BeaconScore is calculated.
curl --request POST \
--url https://beaconcha.in/api/v2/ethereum/validators/performance-aggregate \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"validator": {
"validator_identifiers": [
1
]
},
"range": {
"evaluation_window": "24h"
},
"chain": "mainnet"
}
'{
"data": {
"beaconscore": {
"total": 0.5,
"attestation": 0.5,
"proposal": 0.5,
"sync_committee": 0.5
},
"duties": {
"attestation": {
"included": 123,
"assigned": 123,
"correct_head": 123,
"correct_source": 123,
"correct_target": 123,
"valuable_correct_head": 123,
"valuable_correct_source": 123,
"valuable_correct_target": 123,
"avg_inclusion_delay": 1.2,
"avg_inclusion_delay_excluding_missed_slots": 1.2,
"missed": 123
},
"sync_committee": {
"successful": 1,
"assigned": 1,
"missed": 1
},
"proposal": {
"successful": 123,
"assigned": 123,
"missed": 123,
"included_slashings": 123
}
},
"finality": "not_finalized"
},
"range": {
"slot": {
"start": 1,
"end": 1
},
"epoch": {
"start": 1,
"end": 1
},
"timestamp": {
"start": 1,
"end": 1
}
}
}Authorizations
Body
Free selectors available to all users:
- validator_identifiers: One or more validator indices or public keys to filter by.
- dashboard_id: Your beaconcha.in dashboard ID (requires a free account).
Premium selectors for Scale & Enterprise plans (https://beaconcha.in/pricing):
- withdrawal: The validator's withdrawal credential or the Ethereum wallet address used for withdrawals.
- deposit_address: The Ethereum wallet address used for the validator's deposit.
- Indexes/Public Keys
- Dashboard
- 💎 Deposit
- 💎 Withdrawal
Show child attributes
Show child attributes
An array containing either validator indices or public keys. Index and public key can be mixed in the same array.
Premium users can include up to 100 entries; free users are limited to 20.
1 - 100 elementsValidator Index
x >= 0The Ethereum chain to query.
mainnet, hoodi Response
Successful response.
Response containing the aggregated beaconscore of the validators.
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Number of times the validator's attestation was included on-chain.
This count includes all attestations submitted by the validator, even if they were included too late to earn a reward (such late attestations are still considered "missed" for reward purposes). "Included" reflects every attestation that made it on-chain, regardless of timeliness or eligibility for rewards.
This metric indicates whether your validator is actively submitting attestations to the network.
Number of times the validator was assigned an attestation duty. This represents the total opportunities to attest, regardless of whether the validator fulfilled the duty.
Number of times the validator attested with the correct head block. Correct references are necessary to be rewarded by the chain but incorrect references result in no reward or a penalty.
Number of times the validator attested with the correct source block. Correct references are necessary to be rewarded by the chain but incorrect references result in no reward or a penalty.
Number of times the validator attested with the correct target block. Correct references are necessary to be rewarded by the chain but incorrect references result in no reward or a penalty.
Counts the number of correct head attestations that were included early enough to receive a reward.
Attestations that were included too late to earn a reward (and are treated as missed for reward purposes) are not counted as valuable.
Counts the number of correct source attestations that were included early enough to receive a reward.
Attestations that were included too late to earn a reward (and are treated as missed for reward purposes) are not counted as valuable.
Counts the number of correct target attestations that were included early enough to receive a reward.
Attestations that were included too late to earn a reward (and are treated as missed for reward purposes) are not counted as valuable.
Average inclusion delay measures how quickly a validator's attestations are included in the chain, expressed in slots. Lower values indicate more timely inclusion and better performance.
An ideal value of 0 means every attestation was included at the earliest possible opportunity—one slot after it was assigned to you.
Note: Do not confuse this metric with the reward.inclusion_delay field found in the rewards endpoint, which refers to a specific reward (measured in gwei) that was only applicable prior to the Altair hardfork.
0 <= x <= 631.2
This is your average inclusion delay, excluding any missed blocks.
- If avg_inclusion_delay_excluding_missed_slots is close to zero but avg_inclusion_delay is higher, this indicates that most of your attestations are included promptly, and any lost rewards are primarily due to missed blocks on the network (outside your control).
- If both values are large, it suggests your validator is experiencing delays in submitting attestations, likely due to issues with your validator's setup or connectivity.
Note: avg_inclusion_delay is used for reward calculations. Therefore, an avg_inclusion_delay_excluding_missed_slots of zero does not mean there were no missed rewards.
The avg_inclusion_delay_excluding_missed_slots is always less than or equal to your actual avg_inclusion_delay.
0 <= x <= 631.2
Show child attributes
Show child attributes
Number of times the validator successfully participated in the sync committee.
x >= 0Number of times the validator was assigned to participate in the sync committee.
x >= 0Number of times the validator missed participation in the sync committee.
x >= 0Show child attributes
Show child attributes
Number of times the validator successfully proposed a block.
Number of times the validator was assigned to propose a block.
Number of times the validator either missed a scheduled block proposal or had their proposed block orphaned
Number of slashing proofs included in blocks proposed by the validator. A slashing proof provides cryptographic evidence that one or more validators proposing two different blocks for the same slot.
Indicates the finality status of the data provided.
- Finalized data cannot be changed without slashing at least one-third of all validators, providing strong economic guarantees.
- Data marked as not_finalized does not have this guarantee and may still change.
not_finalized, finalized The range of data covered by the results, specified in slots, epochs, and Unix timestamps.
Show child attributes
Show child attributes
Was this page helpful?