Skip to main content

​
Snapshot by stablecoin

USDC turns over more than its own supply in a day; USDT turns over about 15% of its. That’s a velocity comparison, not a ratio of like quantities. Supply is a closing-balance snapshot and transfer volume is a daily SUM. summarize=true returns the endDate day’s value for each metric here, not a period aggregate; see Core concepts.

​
Metrics

STABLECOIN_DAU, like every *DAU metric, aggregates AVERAGE: a period figure is an average of daily actives, never a summed count.
STABLECOIN_SUPPLY is a closing-balance snapshot: each monthly bucket carries that month’s last day. Verified against the daily series for May 2026 (matches 2026-05-31) and June 2026 (matches 2026-06-30).
Transfer volume reflects gross transfers as of the July 2026 methodology change, and the previously available Artemis-filtered and P2P variants have been retired. See Stablecoin metrics methodology.

​
Split supply by chain

29 rows come back, one per chain, asset named <chain>-usdc (ethereum-usdc, solana-usdc, and so on) with a human-readable display_name. The top eight on 2026-08-01: All 29 rows sum to $73,339,893,117.60, exactly the undifferentiated STABLECOIN_SUPPLY total for usdc on the same day, so this particular cut is a clean partition. That’s worth checking rather than assuming: cuts in /supported-metrics/ lists what a metric advertises, not what it delivers, and a listed dimensionType can still fail to reconcile, or fail outright. Confirm with a live call before publishing a breakdown built on one.

​
Track supply over time

Each month is labelled by its first day, so 2026-06-01 is June’s bucket. That’s the same start-of-period convention every ordinary time series uses (see Core concepts), even though the value inside it is that month’s closing supply, not its opening one. Only three months print for a range that asks for four, because a MONTH bucket resolves once endDate reaches that period’s end. For a period still in progress, it resolves to the most recent day with data. Keep the if v is not None guard: an unresolved bucket comes back as a well-formed row with a null value, the same shape covered in Sector leaderboards.