Metrics

Fees, supply-side fees and revenue, in USD. One row per thing per day, at one grain: chain.

Tables

Daily HyperEVM gas fees and revenue cover closed UTC days and follow HyperEVM’s availability cutoff.

A tab per grain. Coverage shows which chains report which measure.

Chain

One row per chain per day. Every table holds timestamp, chain_id and one value column.

Table	Value column	What it holds
`metrics_chains.fees_daily`	`fees`	Fees paid to the chain (gas / sequencer).
`metrics_chains.fees_supply_side_daily`	`fees_supply_side`	Fees the chain does not retain (pass-throughs to builders / operators); fees = revenue + fees_supply_side. 0 where there are no pass-throughs, e.g. HyperEVM gas.
`metrics_chains.revenue_daily`	`revenue`	Revenue retained by the chain (gas / sequencer fees net of pass-throughs; equals fees where there are none, e.g. HyperEVM).

Sample queries

One chain's series
Monthly fees
Fees by project
Fee split

Each measure is its own table, so a row with both is a join on chain_id and timestamp. Bound the day range on every side, or the unbounded side reads its whole table.

with fees as (
    select timestamp, fees
    from `metrics_chains.fees_daily`
    where chain_id = 'ethereum'
      and timestamp >= timestamp('2026-06-01')
),

revenue as (
    select timestamp, revenue
    from `metrics_chains.revenue_daily`
    where chain_id = 'ethereum'
      and timestamp >= timestamp('2026-06-01')
)

select
    timestamp,
    fees.fees,
    revenue.revenue
from fees
full join revenue
    using (timestamp)
order by timestamp

fees adds up over time, so a month is its days added together. Every table here is partitioned by timestamp and clustered on chain_id, so bounding both reads the least.

select
    timestamp_trunc(timestamp, month) as month,
    sum(fees) as fees
from `metrics_chains.fees_daily`
where chain_id = 'ethereum'
  and timestamp >= timestamp('2026-01-01')
group by month
order by month

These tables key on chain_id alone, so attributing a chain’s fees to the project running it means joining dimensions.chains. A project that runs several chains lands one row, with its chains added together.

select
    chains.project_id,
    sum(daily.fees) as fees
from `metrics_chains.fees_daily` as daily
join `dimensions.chains` as chains
    using (chain_id)
where daily.timestamp = timestamp('2026-08-01')
group by chains.project_id
order by fees desc

fees is revenue plus fees_supply_side. Ethereum burns base and blob fees into revenue and pays priority tips to validators as fees_supply_side, while a chain that keeps all of its gas reads revenue equal to fees.

with fees as (
    select chain_id, fees
    from `metrics_chains.fees_daily`
    where timestamp = timestamp('2026-08-01')
),

revenue as (
    select chain_id, revenue
    from `metrics_chains.revenue_daily`
    where timestamp = timestamp('2026-08-01')
),

supply_side as (
    select chain_id, fees_supply_side
    from `metrics_chains.fees_supply_side_daily`
    where timestamp = timestamp('2026-08-01')
)

select
    chain_id,
    fees.fees,
    revenue.revenue,
    supply_side.fees_supply_side
from fees
left join revenue
    using (chain_id)
left join supply_side
    using (chain_id)
order by fees desc

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Tables

Sample queries

​Tables

​Sample queries

Tables

Sample queries