> ## 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.

# Metrics

> Daily supply, holders, transfers and off-peg, per stablecoin and per deployment.

Daily stablecoin metrics: supply, holders, transfer activity, price and off-peg.

* [`metrics.assets_daily`](/docs/catalog/assets/metrics): one row per stablecoin per day.
* [`metrics.asset_tokens_daily`](/docs/catalog/assets/metrics): one row per deployment per day.

Every column is documented at [Assets ▸ Metrics](/docs/catalog/assets/metrics).

Supply columns come in three reads: `market_cap_circulating_native` counts issuer-minted supply, `market_cap_circulating_bridged` counts the bridged wrappers standing in for supply issued elsewhere, and `market_cap_circulating_total` is the two together. Pick the read you mean; the total counts tokens outstanding rather than economic value.

## Sample queries

<Tabs>
  <Tab title="One stablecoin">
    `off_peg` reads as a decimal fraction of the peg: `-0.02` is two percent below.

    **Read one stablecoin's daily supply, holders, transfer volume and peg deviation.**

    ```sql theme={null}
    select
        timestamp,
        asset_id,
        symbol,
        market_cap_circulating_native,
        holders_native,
        transfer_volume_native,
        off_peg
    from `metrics.assets_daily`
    where asset_type = 'stablecoin'
      and asset_id = 'usdt'
      and timestamp >= timestamp('2026-06-01')
    order by timestamp
    ```

    **Rank stablecoins by native circulating supply on one day.**

    ```sql theme={null}
    select
        symbol,
        market_cap_circulating_native,
        holders_native,
        off_peg
    from `metrics.assets_daily`
    where asset_type = 'stablecoin'
      and timestamp = timestamp('2026-08-01')
      and market_cap_circulating_native is not null
    order by market_cap_circulating_native desc
    limit 25
    ```
  </Tab>

  <Tab title="By chain">
    Supply is native where the issuer minted it, and bridged where someone locked native supply on one chain and issued a stand-in on another. `bridged_status` says which side a deployment sits on.

    **Break one stablecoin's supply down by chain.**

    ```sql theme={null}
    select
        timestamp,
        chain_id,
        bridged_status,
        market_cap_circulating_native,
        market_cap_circulating_bridged,
        transfer_count_native
    from `metrics.asset_tokens_daily`
    where asset_type = 'stablecoin'
      and asset_id = 'usdc'
      and timestamp = timestamp('2026-08-01')
    order by market_cap_circulating_native desc
    ```

    **Compare stablecoin supply across chains on one day.**

    ```sql theme={null}
    select
        chain_id,
        count(distinct asset_id) as stablecoins,
        sum(market_cap_circulating_native) as native_supply
    from `metrics.asset_tokens_daily`
    where asset_type = 'stablecoin'
      and timestamp = timestamp('2026-08-01')
    group by chain_id
    order by native_supply desc
    ```
  </Tab>

  <Tab title="Asset against deployments">
    **Check a stablecoin's supply against the sum of its deployments.**

    ```sql theme={null}
    select
        panel.timestamp,
        panel.market_cap_circulating_native as asset_grain,
        deployments.summed as deployment_grain
    from `metrics.assets_daily` as panel
    join (
        select
            asset_id,
            timestamp,
            sum(market_cap_circulating_native) as summed
        from `metrics.asset_tokens_daily`
        where asset_id = 'usdt'
        group by asset_id, timestamp
    ) as deployments
        using (asset_id, timestamp)
    where panel.asset_id = 'usdt'
      and panel.timestamp >= timestamp('2026-08-01')
    order by panel.timestamp
    ```

    Circulating supply is the one measure where the two sides can differ, and the difference is deliberate. Some issuers report supply that no token contract represents, so the stablecoin's row includes that part while no deployment's row does. `market_cap_circulating_offchain` publishes that part on its own, so the gap is always explainable.
  </Tab>
</Tabs>