Metrics - Token Terminal Docs

metrics_tokens.price_daily holds one row per token per day: the price in USD at midnight UTC. metrics_tokens.price_hourly holds the same figure at the top of every hour.

Columns

Both tables share one schema.

Column	Type	Description
`timestamp`	`TIMESTAMP`	The moment the price was taken: midnight UTC in the daily table, the top of the hour in the hourly one.
`token_id`	`STRING`	Token the price belongs to: `{token_address}-{chain_id}`. Joins `dimensions.tokens`.
`chain_id`	`STRING`	Chain the token is deployed on.
`price`	`FLOAT64`	The price in US dollars at that moment. Every row has a value, and a token has a row on each day it was priced, so a null after a left join is a missing row.

Sample queries

Daily
Hourly

The daily table suits long histories and joins to the other daily tables at a fraction of the hourly table’s size. token_id is the key on both sides of the join.

select
    prices.timestamp,
    tokens.symbol,
    tokens.name,
    prices.price
from `metrics_tokens.price_daily` as prices
join `dimensions.tokens` as tokens
    using (token_id)
where prices.token_id = '0xdac17f958d2ee523a2206206994597c13d831ec7-ethereum'
  and prices.timestamp >= timestamp('2026-07-01')
order by prices.timestamp

The hourly table suits analysis within a day, and pricing individual events. Both tables key the same way, so moving a query between them means swapping the table name and the time bounds.

select
    timestamp,
    price
from `metrics_tokens.price_hourly`
where token_id = '0xdac17f958d2ee523a2206206994597c13d831ec7-ethereum'
  and timestamp >= timestamp('2026-08-20')
  and timestamp < timestamp('2026-08-23')
order by timestamp