Block Rewards

The ethereum.raw.block_rewards model provides enriched block-level data of the various types of protocol-level rewards to the miners (block builder) and block proposers (validator), pre and most-merge.

Update: 2024-05-20 — Pre-merge backfill and reward precision

This table is updated to include pre-merge block-level rewards.
All columns with ETH values (rewards) in this table are kept in string format to retain precision.

Update: 2026-07-28 — MEV payout detection correction

Added a third detection signal for has_mev_reward / proposer_mev_reward: MEV payouts that a builder routes through a separate payout wallet (distinct from the block’s builder_address) are now recognized. Previously, these blocks were misclassified as non-PBS, and the model attributed the builder’s full gross capture (priority fees + direct transfers) to the proposer instead of the actual, smaller MEV payout.
Why this happened: has_mev_reward is inferred from on-chain heuristics rather than an authoritative source. The original logic recognized a payout only when it was sent directly from the block’s builder address, or directly to the validator’s beacon withdrawal address. Some builders route the payout through a separate wallet that is neither address, so those blocks fell through both checks.
Scope: across the post-Merge period, roughly 4% of validator-days have a changed proposer_mev_reward / has_mev_reward, affecting about 15% of validators that have ever proposed a block. In aggregate, total proposer_mev_reward across the period is reduced by roughly 1.2%. For most affected validator-days the change is a few thousandths of an ETH; a smaller number of validator-days, concentrated among a handful of large builders, were overstated by tens to hundreds of ETH.
Historical block_rewards is being backfilled for all post-Merge blocks (September 15, 2022 onward). This table is incremental, so historical values will only update once the backfill runs — not on the next regular refresh.

Known limitations of MEV payout detectionhas_mev_reward is inferred from on-chain heuristics, not from MEV-boost relay bid-trace data — the authoritative record of what a builder actually paid a proposer. Allium does not currently ingest relay bid-trace data, so some edge cases can still be missed:

A builder’s separate payout wallet is only trusted once it has an established track record of paying known validator withdrawal addresses. A wallet’s first several payouts, before that track record accumulates, may not yet be recognized as an MEV payout.
Detection can improve as more payout history accumulates over time, so a given historical block’s classification is not guaranteed to be stable until any pending backfill has completed.
A payout that is not the block’s last transaction, or that is split across multiple transactions, is not recognized as an MEV payout by any of the three detection rules above.
Detection only adds newly-recognized MEV payouts as heuristics improve — it does not remove a payout that was already correctly detected.

We treat MEV detection as an evolving heuristic rather than a finished one, and expect to keep refining it — including a longer-term plan to ingest relay bid-trace data directly.

Block-level ETH rewards on Ethereum can be separated into various types:

Miner (block builder)
- Pre-merge
  - Block rewards from protocol emissions.
    - For each block, the miner is rewarded with a finite amount of Ether on top of the fees paid.
  - Uncle rewards
    - Uncles reward is valid but rejected as it is not on the longest chain which is the working mechanism of the blockchain.
- Transaction priority fee
- Direct transfers from transaction senders to block builder
Proposer (MEV post-merge)
- Amount of MEV reward received by the block proposer, and the corresponding index of the validator that proposed the block
- MEV rewards are identified using the following logic:
  - If the last transaction of the block is sent from the block builder (miner), this is assumed to be an MEV payout
  - If the last transaction of the block is sent to the withdrawal address of the validator that proposed the block, this is also captured as an MEV payout
  - If the last transaction of the block is a direct ETH transfer to a different, non-self address, and the sender is a wallet with an established history of paying MEV payouts to known validator withdrawal addresses on behalf of that same builder (a “payout wallet”), this is also captured as an MEV payout. This catches builders that route the proposer payout through a wallet other than their own block fee-recipient address — the sender differs from builder_address, and the recipient differs from the beacon withdrawal address, so neither of the first two rules applies.
- Example: https://etherscan.io/block/19900222#mevinfo

Sample Query

Examine block-level rewards by reward type on Ethereum over time.

select
    date_trunc('week', block_timestamp) as date,
    sum(block_reward) as block_reward,
    sum(uncles_reward) as uncles_reward,
    sum(builder_priority_fee_reward) as builder_priority_fee_reward,
    sum(builder_direct_reward) as builder_direct_reward,
    sum(proposer_mev_reward) as proposer_mev_reward
from ethereum.raw.block_rewards
group by all

Table Columns

Unique key: block_number

Column Name	Description	Example
block_number	The block number.	17,828,815
block_timestamp	The unix timestamp for when the block was collated.	2023-08-02 17:30:47
has_block_reward	Boolean flag indicating that there is a block reward pre-merge.	FALSE
block_reward	Amount of block rewards to the miner in ETH.	0
has_uncle_reward	Boolean flag indicating that there is a uncle reward pre-merge.	FALSE
uncles_reward	Amount of block uncle rewards in ETH. Note that it is possible to have more than one uncles rewards recipient.	0
uncles_reward_transactions	The trace level transfers to the uncles reward recipient wrapped in JSON.	NULL
base_fee_burnt	ETH burnt from base fee gas amount.	0.4084471863
builder_priority_fee_reward	Priority fee (tips) to the block builder (miner) recipient address.	0.02960400525
builder_direct_reward	Direct ETH transfers rewarded to the block builder (miner) in the block.	0.0002492600004
builder_address	Block builder (miner) address.	0xdafea492d9c6733ae3d56b7ed1adb60692c98bc5
builder_direct_transactions	Array of direct ETH transactions to the block producer in the block, assumed to be builder’s direct rewards.	`[{"amount":"0.000249260000412","eth_from_address":"0x0c3de458b51a11da7d4616f42f66c861e3859d3e","transaction_from_address":"0x26fd09c8b44af53df38a9bad41d5abc55a1786af","transaction_hash":"0xf766b52...","transaction_to_address":"0x0c3d...","usd_amount":"0.45555"}]`
has_mev_reward	Boolean flag indicating whether there is an MEV reward, sent from the block builder (or a wallet acting on its behalf) to the block proposer fee recipient in the last transaction of the block. See “MEV rewards are identified using the following logic” above.	TRUE
proposer_mev_reward	Proposer’s MEV reward sent from the block builder.	0.02926816803
proposer_fee_recipient	Block proposer fee recipient address.	0x388c818ca8b9251b393131c08a736a67ccb19297
proposer_payout_transaction	Proposer’s MEV reward payout transaction.	0x4186fa75972f93882acf7c9630eaee05c21132fba8d97a0826dc78b1e1cf1464
l1_gas_used	L1 gas used.	15,435,342
l1_gas_limit	L1 gas limit of the block.	30,000,000
l1_extra_data	L1 extra data.	0x496c6c756d696e61746520446d6f63726174697a6520447374726962757465
l1_block_hash	L1 block hash.	0x69b5ed627b2a16c7e13446b6cab4159ef1e850a4f9d64b66a31225d2e24b4d2f
slot_number	Beacon Chain slot number.	7,014,452
epoch	Beacon Chain epoch number.	219,201
proposer_index	Validator Index of the block proposer on Beacon Chain.	277,565
pubkey	Pubkey of the validator proposing this block.	0xb7be38a5fcc9400c3c4b7dace7c0ae75ca76d47ce0e8de5177e38786b8bf71c5b03889ab3c4c436b731f4df01f398b78
graffiti	32-byte field of arbitrary data included by the block proposer.	0x0000000000000000000000000000000000000000000000000000000000000000

Overview

Data Verticals

Solana

Hyperliquid

Lighter

Bitcoin Ecosystem

EVM

Cosmos Ecosystem

Move Ecosystem

Other Ecosystems

Sample Query

Table Columns

​Sample Query

​Table Columns

Sample Query

Table Columns