curl --request GET \
--url 'https://beaconcha.in/api/v1/validator/{indexOrPubkey}/execution/performance?apikey='{
"status": "OK",
"data": [
{
"performance1d": 470167509840,
"performance7d": 7470167509840,
"performance31d": 357470167509840,
"performance365d": 10357470167509840,
"performanceTotal": 438451008639390900,
"validatorindex": 20
}
]
}Retrieve execution-layer rewards (priority fees and MEV payments) for one or more validators over multiple lookback windows. Provide validator identifiers as a comma-separated list in the path parameter. The service accepts validator indices and 0x-prefixed BLS pubkeys (up to the server-enforced limit; default 100). Values are reported in wei.
curl --request GET \
--url 'https://beaconcha.in/api/v1/validator/{indexOrPubkey}/execution/performance?apikey='{
"status": "OK",
"data": [
{
"performance1d": 470167509840,
"performance7d": 7470167509840,
"performance31d": 357470167509840,
"performance365d": 10357470167509840,
"performanceTotal": 438451008639390900,
"validatorindex": 20
}
]
}Comma-separated validator indices and/or public keys (maximum 100 items by default). Comma-separated list (no spaces) of validator identifiers. Each identifier must be either:
Resolution and limits:
"1,2,3"
Matching validators were retrieved successfully. The data array contains one item per validator with execution-layer reward totals for the last 1, 7, and 31 days, the last 365 days, and the cumulative sum since genesis when available.
Was this page helpful?