> For the complete documentation index, see [llms.txt](https://docs.everstake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.everstake.com/integrations/everstake-products/data-product-deprecated/ethereum.md).

# Ethereum

<details>

<summary>General Information</summary>

<table data-header-hidden><thead><tr><th width="337.75"></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td>Refresh Frequency</td><td>Daily at 12:01 UTC</td><td></td></tr><tr><td>Status</td><td>Supporting</td><td></td></tr><tr><td>Support</td><td>account-data-support@everstake.one</td><td></td></tr><tr><td>Contact</td><td>contact@everstake.one</td><td></td></tr></tbody></table>

</details>

***

## Overview

This dataset empowers businesses and investors to strategically monitor Ethereum staking behavior, gain near real-time insights into validator performance, and optimize reward-based investment decisions. By analyzing metrics such as APR, staked amounts, and consensus/execution layer rewards, you can uncover patterns in on-chain activity that support portfolio management and yield optimization.

Whether you’re evaluating validator reliability, identifying top-performing validators for staking, or predicting market trends based on staking dynamics, our comprehensive Ethereum staking data provides a robust foundation for actionable insights.

***

## Tables

<details>

<summary>APR</summary>

{% hint style="success" %}

#### Business value and potential connections

Provides insights into validator profitability by calculating annual percentage rates (APR) and rewards from both the consensus and execution layers. It helps track staking returns over time.

> **Can be JOINed with** `VALIDATORS` (for validator details) and `STAKE` (to analyze staking and reward relationships).
> {% endhint %}

<table data-full-width="false"><thead><tr><th width="182.111083984375">Column</th><th width="138.361083984375">Type</th><th>Description</th></tr></thead><tbody><tr><td>CL_APR</td><td>Number</td><td>Consensus layer APR</td></tr><tr><td>CL_REWARD</td><td>Number</td><td>Consensus layer reward</td></tr><tr><td>DATE</td><td>Date</td><td>Date of the record</td></tr><tr><td>EL_APR</td><td>Number</td><td>Execution layer APR</td></tr><tr><td>EL_REWARD</td><td>Number</td><td>Execution layer reward</td></tr><tr><td>TOTAL_APR</td><td>Number</td><td>Total APR (CL + EL)</td></tr><tr><td>TOTAL_REWARD</td><td>Number</td><td>Total reward (CL + EL)</td></tr><tr><td>VALIDATOR_INDEX</td><td>Number</td><td>The index of the validator</td></tr></tbody></table>

</details>

<details>

<summary>DIMENSIONS</summary>

{% hint style="success" %}

#### Business value and potential connections

Provides essential blockchain structure data (epochs, slots, blocks), supporting time-based analytics and event tracking.

> **Can be JOINed with** `VALIDATOR_CL_REWARDS`, `VALIDATOR_EL_REWARDS`, and `STAKE` (to enrich all historical data with epoch and slot context).
> {% endhint %}

<table data-full-width="false"><thead><tr><th width="161">Column</th><th width="167.25">Type</th><th>Description</th></tr></thead><tbody><tr><td>BLOCK_FROM</td><td>Number</td><td>Starting block number</td></tr><tr><td>BLOCK_TO</td><td>Number</td><td>Ending block number</td></tr><tr><td>DIM_NAME</td><td>Varchar</td><td>Dimension name in this case is the constant 'epoch'</td></tr><tr><td>DIM_NUMBER</td><td>Number</td><td>Epoch number</td></tr><tr><td>SLOT_FROM</td><td>Number</td><td>Starting slot number</td></tr><tr><td>SLOT_TO</td><td>Number</td><td>Ending slot number</td></tr><tr><td>TIME_FROM</td><td>Timestamp_NTZ</td><td>Start timestamp</td></tr><tr><td>TIME_TO</td><td>Timestamp_NTZ</td><td>End timestamp</td></tr></tbody></table>

</details>

<details>

<summary>STAKE</summary>

{% hint style="success" %}

#### Business value and potential connections

Tracks staking activity, including delegations and undelegations, allowing analysis of validator participation and delegation trends. Helps monitor capital flows in staking ecosystems.

> **Can be JOINed with** `VALIDATORS` (to get validator details) and `APR` (to compare staking activity with APR and rewards).
> {% endhint %}

<table data-full-width="false"><thead><tr><th width="164.75">Column</th><th width="157.5">Type</th><th>Description</th></tr></thead><tbody><tr><td>AMOUNT</td><td>Number</td><td>Delegated amount (positive for delegation, negative for undelegation)</td></tr><tr><td>BLOCK</td><td>Number</td><td>Block number where the transaction occurred</td></tr><tr><td>CREATED_AT</td><td>Timestamp_NTZ</td><td>Timestamp when the record was created</td></tr><tr><td>CURRENCY</td><td>Varchar</td><td>Staked currency (ETH)</td></tr><tr><td>DELEGATOR</td><td>Varchar</td><td>Address of the delegator</td></tr><tr><td>DIM_NAME</td><td>Varchar</td><td>Dimension name used for indexing</td></tr><tr><td>DIM_NUMBER</td><td>Number</td><td>Dimension value</td></tr><tr><td>EPOCH</td><td>Number</td><td>Epoch associated with the validator</td></tr><tr><td>EVENT_INDEX</td><td>Number</td><td>Index of the event in the block</td></tr><tr><td>HASH</td><td>Varchar</td><td>Unique transaction hash (66-character identifier)</td></tr><tr><td>INSERTED_TIME</td><td>Timestamp_NTZ</td><td>The UTC timestamp at which the row was inserted into the table</td></tr><tr><td>MODIFIED_TIME</td><td>Timestamp_NTZ</td><td>The UTC timestamp at which the row was last modified</td></tr><tr><td>TYPE</td><td>Varchar</td><td>Type of transaction (<code>delegation</code> or <code>undelegation</code>)</td></tr><tr><td>VALIDATOR</td><td>Varchar</td><td>Public key of the validator</td></tr></tbody></table>

</details>

<details>

<summary>VALIDATORS</summary>

{% hint style="success" %}

#### Business value and potential connections

Stores validator metadata, including public keys, operator names, and activity status, enabling entity-level performance analysis.

> **Can be JOINed with** `VALIDATOR_CL_REWARDS`, `VALIDATOR_EL_REWARDS`, `STAKE` , and `APR` (to get validator-specific insights).
> {% endhint %}

<table data-full-width="false"><thead><tr><th width="217.25">Column</th><th width="153.75">Type</th><th>Description</th></tr></thead><tbody><tr><td>ACTIVE_DATE</td><td>Timestamp_NTZ</td><td>Timestamp when the validator became active</td></tr><tr><td>ENTITY</td><td>Varchar</td><td>Name of the organization or entity operating the validator</td></tr><tr><td>ENTITY_CATEGORY</td><td>Varchar</td><td>Category of the entity (e.g., CEX for centralized exchange)</td></tr><tr><td>ENTITY_GROUP</td><td>Varchar</td><td>Group the entity belongs to</td></tr><tr><td>ENTITY_UNIQUE_NAME</td><td>Varchar</td><td>Unique identifier for the entity</td></tr><tr><td>EXIT_DATE</td><td>Timestamp_NTZ</td><td>Timestamp when the validator exited</td></tr><tr><td>LIDO_OPERATOR_NAME</td><td>Varchar</td><td>Name of the Lido operator</td></tr><tr><td>POOL</td><td>Varchar</td><td>Name of the staking pool the validator is part of</td></tr><tr><td>PUBKEY</td><td>Varchar</td><td>Validator's public key</td></tr><tr><td>VALIDATOR_INDEX</td><td>Number</td><td>Unique identifier for the validator</td></tr></tbody></table>

</details>

<details>

<summary>VALIDATOR_CL_REWARDS</summary>

{% hint style="success" %}

#### Business value and potential connections

Provides insights into validator rewards at the consensus layer, useful for tracking staking profitability and historical earnings.

> **Can be JOINed with** `VALIDATORS` (to get validator details) and `VALIDATOR_EL_REWARDS` (for total validator income analysis).
> {% endhint %}

<table data-full-width="true"><thead><tr><th width="178.5">Column</th><th width="175.25">Type</th><th>Description</th></tr></thead><tbody><tr><td>DATE</td><td>Date</td><td>Reward received date</td></tr><tr><td>INSERTED_TIME</td><td>Timestamp_NTZ</td><td>The UTC timestamp at which the row was inserted into the table</td></tr><tr><td>MODIFIED_TIME</td><td>Timestamp_NTZ</td><td>The UTC timestamp at which the row was last modified</td></tr><tr><td>REWARDS</td><td>Number</td><td>Consensus layer reward</td></tr><tr><td>VALIDATOR_INDEX</td><td>Number</td><td>Validator index that earned a reward</td></tr></tbody></table>

</details>

<details>

<summary>VALIDATOR_EL_REWARDS</summary>

{% hint style="success" %}

#### Business value and potential connections

Captures execution layer rewards, including MEV and block production incentives, helping analyze additional validator revenue streams.

> **Can be JOINed with** `VALIDATORS` (to identify validator operators) and `VALIDATOR_CL_REWARDS` (for total validator income analysis).
> {% endhint %}

<table data-full-width="false"><thead><tr><th width="199.75">Column</th><th width="166.5">Type</th><th>Description</th></tr></thead><tbody><tr><td>BLOCK_NUMBER</td><td>Number</td><td>Block number</td></tr><tr><td>BLOCK_REWARD</td><td>Number</td><td>Block reward amount</td></tr><tr><td>INSERTED_TIME</td><td>Timestamp_NTZ</td><td>The UTC timestamp at which the row was inserted into the table</td></tr><tr><td>MEV_REWARD</td><td>Number</td><td>Execution layer reward</td></tr><tr><td>MODIFIED_TIME</td><td>Timestamp_NTZ</td><td>The UTC timestamp at which the row was last modified</td></tr><tr><td>PRODUCER_REWARD</td><td>Number</td><td>Reward for block producer</td></tr><tr><td>RELAY_TAG</td><td>Varchar</td><td>MEV relay identifier</td></tr><tr><td>SLOT_NUMBER</td><td>Number</td><td>Slot number</td></tr><tr><td>SLOT_STATUS</td><td>Number</td><td>Status of the slot, where 1='Proposed', 2='Missed' and 3='Missed (Orphaned)'</td></tr><tr><td>TIMESTAMP</td><td>Timestamp_NTZ</td><td>The date and time at which the block was produced</td></tr><tr><td>VALIDATOR_INDEX</td><td>Number</td><td>Validator index that earned a reward</td></tr></tbody></table>

</details>

***

## Query examples

{% tabs %}
{% tab title="Get validator CL rewards" %}

```sql
select * from VALIDATOR_CL_REWARDS
where VALIDATOR_INDEX=1234567
```

{% endtab %}

{% tab title="Get active validators by entity/operator" %}

```sql
select * from VALIDATORS
where ENTITY='Everstake' and EXIT_DATE is null and ACTIVE_DATE is not null 
```

{% endtab %}

{% tab title="Get last week network(CL+EL) APR" %}

```sql
select DATE,
       AVG(TOTAL_APR) AS NETWORK_APR
from APR
WHERE DATE >= DATEADD(day, -7, CURRENT_DATE())
GROUP BY DATE
```

{% endtab %}
{% endtabs %}

***

## FAQ

<table data-header-hidden><thead><tr><th width="189"></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>1. What does this dataset cover?</strong></td><td>This dataset includes detailed information on Ethereum staking rewards, validator activity, delegations, and withdrawals. It allows users to analyze staking profitability, track validator performance, and assess capital movements in Ethereum’s proof-of-stake ecosystem.</td><td></td></tr><tr><td><strong>2. How can this data benefit staking providers and investors?</strong></td><td><p></p><ul><li><strong>Staking providers</strong> can monitor validator efficiency, optimize operations, and improve reward distribution.</li><li><strong>Investors</strong> can analyze staking inflows/outflows, estimate potential returns, and identify top-performing validators.</li></ul></td><td></td></tr><tr><td><strong>3. What’s the difference between Consensus Layer and Execution Layer rewards?</strong></td><td><p></p><ul><li><strong>Consensus Layer Rewards (<code>VALIDATOR_CL_REWARDS</code>)</strong> come from Ethereum’s proof-of-stake mechanism and are earned for validating blocks.</li><li><strong>Execution Layer Rewards (<code>VALIDATOR_EL_REWARDS</code>)</strong> include transaction fees and MEV, offering additional income opportunities.</li></ul></td><td></td></tr><tr><td><strong>4. How can this dataset help detect validator risks?</strong></td><td>By analyzing validator withdrawals (<code>STAKE</code>, for undelegations) and performance trends (<code>VALIDATOR_CL_REWARDS</code> + <code>VALIDATOR_EL_REWARDS</code>), businesses can detect declining validators, risk of slashing, or validators experiencing high churn.</td><td></td></tr><tr><td><strong>5. Can I track individual validator performance?</strong></td><td>Yes. The <code>VALIDATORS</code> table can be <strong>JOINed</strong> with rewards (<code>VALIDATOR_CL_REWARDS</code>, <code>VALIDATOR_EL_REWARDS</code>), delegations, and withdrawals (<code>STAKE</code>) to analyze each validator's earnings, activity, and staking inflows.</td><td></td></tr><tr><td><strong>6. How does the historical blockchain data help?</strong></td><td>The <code>STAKE</code> table provides <strong>block, event, and epoch-level data</strong>, which is essential for tracking when rewards were earned, how staking activity changed over time, and correlating events with on-chain activity. Additionally, the <code>DIMENSIONS</code> table helps structure this data by providing contextual details for better analysis and historical tracking.</td><td></td></tr><tr><td><strong>7. How frequently is the data updated?</strong></td><td>The dataset updates <strong>daily at 12:01 UTC</strong>, ensuring accurate and timely access to Ethereum staking metrics.</td><td></td></tr></tbody></table>

***

## Links

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-type="files"></th></tr></thead><tbody><tr><td><a href="https://everstake.one/staking/ethereum">Stake with Everstake</a></td><td><a href="https://1249209355-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyXGefmWNIENxOOHmKgY%2Fuploads%2FyWN8N0revZW0x4Gnn87T%2F%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%BD%D1%8F_2025-03-21_001348788.png?alt=media&amp;token=3fae7594-dfda-4be4-9095-6e4367735a84">зображення_2025-03-21_001348788.png</a></td><td></td></tr><tr><td><a href="https://dune.com/everstake1/everstake-eth-staking">Everstake ETH dashboard on Dune</a></td><td><a href="https://1249209355-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyXGefmWNIENxOOHmKgY%2Fuploads%2FyWN8N0revZW0x4Gnn87T%2F%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%BD%D1%8F_2025-03-21_001348788.png?alt=media&amp;token=3fae7594-dfda-4be4-9095-6e4367735a84">зображення_2025-03-21_001348788.png</a></td><td></td></tr><tr><td><a href="https://app.powerbi.com/groups/fc109ba3-938a-49da-96ee-7fdc37f4a65a/reports/bc0f6766-a592-4f9c-ab6a-54568076b8f4/ReportSection34d6fc37ea08aac3280a?experience=power-bi">Everstake ETH dashboard on PowerBI</a></td><td><a href="https://1249209355-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyXGefmWNIENxOOHmKgY%2Fuploads%2FyWN8N0revZW0x4Gnn87T%2F%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%BD%D1%8F_2025-03-21_001348788.png?alt=media&amp;token=3fae7594-dfda-4be4-9095-6e4367735a84">зображення_2025-03-21_001348788.png</a></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.everstake.com/integrations/everstake-products/data-product-deprecated/ethereum.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.