> ## Documentation Index > Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > To query the Token Terminal data catalog, read https://tokenterminal.com/docs/catalog/agents-manual.md first. It is the whole catalog as one page: table naming grammar, key columns, partition and cluster rules, units, additivity, and the tables that are documented but not served yet. > Never query a catalog table on a time bound alone. Also filter its cluster key, which you read from INFORMATION_SCHEMA.COLUMNS; an empty result means the object is a view, whose pruning contract is on its page. Compute is billed to the caller's own Google Cloud project. # Screener > Every chain's latest figures and its apps' figures, with averages, totals and changes over six windows, in one row. One row per chain in `screeners.chains`, every figure as of `as_of`, the last complete day. Each measure has a column per window and aggregation, named `__`: `fees_30d_sum` is the fees paid to the chain over the 30 days ending on `as_of`, and `app_fees_30d_sum` is the fees paid to the apps on it. ## Columns The two key columns, then one FLOAT64 column per measure, window and aggregation. Every row is a chain in `dimensions.chains`, so the join on `chain_id` always matches.
Column Type Description
as\_ofTIMESTAMPThe last complete day, the same on every row. Every window ends on it.
chain\_idSTRINGChain the row belongs to, such as ethereum; joins dimensions.chains.
A window is `1d`, `7d`, `30d`, `90d`, `180d` or `365d`, and spans that many days ending on `as_of`, while the `max_` columns read the whole history. Which aggregations a measure has follows its `over_time` in [Metric definitions](/docs/catalog/metric-definitions): only a measure whose `over_time` is `sum` has `sum`.
Column What it holds
\\_\\_avgMean of the daily values over the window.
\\_\\_sumTotal of the daily values over the window. Flows only: the measures ticked under Sum.
\\_\\_changeA comparison of two aggregations: the value on as\_of against the value one window earlier, as (now - then) / abs(then). Null when either value is missing or the earlier one is 0.
\\_\\_trendA comparison of two aggregations: the window's average against the average of the window before it, as (avg - prior) / abs(prior). Null unless the window before has a value on every one of its days, and null when its average is 0.
\\_max\_latestThe value on as\_of. Null when there is none.
\\_max\_athThe highest daily value over the chain's whole history.
\\_max\_atlThe lowest daily value over the chain's whole history.
Every measure has the `avg`, `change`, `trend` and `max_` columns, and the flows also have `sum`. The `app_` measures are the apps on the chain added together. Price, market cap and developers sit on the [project screener](/docs/catalog/projects/screener), for the project `dimensions.chains` names in `project_id`.
Measure Sum What it holds
daily\_active\_addresses✗Distinct addresses transacting on the chain per day.
monthly\_active\_addresses✗Distinct addresses transacting on the chain over a rolling 30 days.
weekly\_active\_addresses✗Distinct addresses transacting on the chain over a rolling 7 days.
app\_monthly\_active\_addresses✗Distinct addresses using the apps' contracts on the chain over a rolling 30 days, each app's count added up, so an address using two apps counts twice.
app\_active\_loans✗Open loans in the apps on the chain, USD.
app\_assets\_staked✗Assets staked with the apps on the chain, USD.
app\_bridged\_supply✗Stablecoins bridged onto the chain, USD.
app\_fees✓Fees paid to the apps on the chain, USD.
app\_gas\_used✓Gas consumed by transactions calling the apps' contracts on the chain.
app\_outstanding\_supply✗Stablecoin supply issued on the chain, USD.
app\_trading\_volume✓Trading volume of the exchanges on the chain, USD. Derivatives venues and aggregators are left out: an aggregator's volume is counted at the exchange it routes to.
app\_transaction\_count\_contracts✓Transactions calling the apps' contracts on the chain.
app\_tvl✗Value locked in the apps on the chain, USD.
app\_monthly\_active\_users✗Monthly active users of the apps on the chain, each app's count added up, so a user of two apps counts twice.
block\_time\_average✗Average time between blocks.
bridge\_deposits✗USD value of assets held in the chain's canonical bridge on the chain it settles to.
daily\_contract\_deployers✗Distinct addresses deploying contracts.
contract\_deployment\_count✓Contracts deployed on the chain.
cost\_of\_revenue✓The chain's direct cost of revenue, such as data posted to the chain it settles to.
expenses✓What the chain spent, in USD.
fees✓Fees paid to the chain (gas / sequencer).
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.
validators✗Number of validators securing the chain's consensus.
revenue✓Revenue retained by the chain (gas / sequencer fees net of pass-throughs; equals fees where there are none, e.g. HyperEVM).
staking\_market\_cap✗USD value of the chain's native token staked to secure the network.
token\_incentives✓Value of tokens the chain distributed as incentives.
transaction\_count✓Transactions processed by the chain.
transaction\_fee\_average✗Average fee per transaction.
transaction\_fee\_median✗Median fee per transaction.
transactions\_per\_second✗Average transactions per second.
## Sample queries Every column of one row shares the same `as_of`, so the figures read together. `fees` is what users paid the chain, and `app_fees` what they paid the apps running on it. ```sql theme={null} select as_of, fees_30d_sum, app_fees_30d_sum, transaction_count_30d_sum, app_tvl_max_latest, app_tvl_30d_change from `screeners.chains` where chain_id = 'ethereum' ``` `app_fees_30d_sum` is the fees paid to the apps on the chain over the 30 days ending on `as_of`. The join to `dimensions.chains` on `chain_id` adds the name. ```sql theme={null} select chains.name, screener.app_fees_30d_sum, screener.transaction_count_30d_sum, screener.app_fees_30d_trend from `screeners.chains` as screener join `dimensions.chains` as chains using (chain_id) where screener.app_fees_30d_sum is not null order by screener.app_fees_30d_sum desc limit 25 ``` Both sides are 30-day totals over the same window, so their ratio compares the gas users paid the chain with the fees they paid its apps. The app fee floor keeps a small base from dominating the ranking. ```sql theme={null} select chains.name, screener.fees_30d_sum, screener.app_fees_30d_sum, safe_divide(screener.fees_30d_sum, screener.app_fees_30d_sum) as chain_to_app_fees from `screeners.chains` as screener join `dimensions.chains` as chains using (chain_id) where screener.app_fees_30d_sum > 100000 order by chain_to_app_fees desc limit 25 ``` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.