Stablecoin List Ranked by Circulating Supply
Every tracked stablecoin with its issuer, peg, backing, chains and circulating supply, in one table you can sort and filter.
Multi-chainEthereumTron+2Table · StrataPlanned
Stablecoin Contract Addresses: USDT, USDC and More by Chain
What is the official contract address of USDT, USDC and other stablecoins on each chain, and is it native or bridged?
The official contract of every tracked stablecoin on each chain, with issuer, decimals, native or bridged status, admin powers and supply.
ShareEmail it
Blueprint
What the table will hold.
The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
One row One row per stablecoin contract per chain, with supply on the latest complete daySorted by Supply, highest first
| Stablecoin | Issuer | Peg | Chain | Contract | Issuance | Decimals | Upgradeable | Freeze powers | Supplytokens | Receipt |
|---|---|---|---|---|---|---|---|---|---|---|
- Stablecoin stablecoin Token
- The token's name and symbol as its contract reports them.
- Issuer issuer Text
- The firm or protocol that issues the stablecoin.
- Peg peg Text
- The currency the stablecoin tracks.
- Chain chain Chain
- The chain this contract lives on.
- Contract contract Address
- The token contract address, from the registry and confirmed on-chain.
- Issuance issuance Text
- Native, bridged or a cross-chain standard, with the bridge or standard named.
- Decimals decimals Number
- The decimals the contract reports, which scale every amount.
- Upgradeable upgradeable Text
- Whether the contract is a proxy whose code can be changed, and who can change it.
- Freeze powers freeze_powers Text
- Whether the issuer can block addresses or destroy blocked balances.
- Supply supply Exact amount
- totalSupply() at the latest day-end block, scaled by decimals.
- Receipt receipt Link
- The reads behind the row, metadata, proxy slot and supply, with their block.
Filter by Stablecoin, Chain, Issuance.
About
What it answers, and for whom.
Sending a stablecoin to the wrong contract, or trusting a lookalike token with the same name, is an easy mistake to make and often impossible to undo. This table lists the official contract of each tracked stablecoin on every covered chain, from the same registry Voltfin reads supply from, checked against the chain so the address you copy is the one the issuer deployed.
Each row also says what kind of token it is: issued natively by its issuer, bridged from another chain or moved through a cross-chain standard such as CCTP or an OFT. It shows the token's decimals, whether its contract can be upgraded, whether the issuer can freeze balances and its supply today, so developers and treasury teams can tell two USDCs apart.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- Each contract comes from the stablecoin registry, maintained from issuer documentation, and is confirmed on-chain by reading its name(), symbol() and decimals().
- Native means the issuer mints on that chain directly; bridged means a bridge mints a copy against tokens locked elsewhere; cross-chain standards such as CCTP and OFTs are named.
- Upgradeability is read from the proxy's implementation slot, and freeze powers from the contract's blacklist or freeze functions and their past events.
- Supply is totalSupply() at the latest day-end block, scaled by decimals: the same read the stablecoin supply pages use.
The data it needs
Read from chain state and history
- stablecoinsPublishedStablecoin registryEvery tracked stablecoin contract: issuer, peg, chain, decimals and whether it is native or bridged.
- stablecoin_supply_dailyPublishedStablecoin supply by token and chainNative supply of each USD and EUR stablecoin on each covered chain at the chain's last block of each day, from totalSupply() reads, with bridged copies kept apart.
- stablecoin_freezesTo buildStablecoin freezes and blacklistsAddresses frozen or blacklisted by stablecoin issuers, the balances frozen, and later unfreezes or destroyed funds, per stablecoin and chain.
- The stablecoin registry: issuer, peg, chain, decimals and native or bridged status
- name(), symbol() and decimals() read from each contract
- The proxy implementation slot of each upgradeable contract
- totalSupply() at day-end blocks, as published in the stablecoin supply tables
Questions
Questions people ask.
How do I know a stablecoin contract is the official one?
Check it against the issuer's own documentation and against a source that reads the chain. This table takes each contract from a registry built from issuer documentation and confirms it on-chain. A token with the right name at a different address is not the issuer's token.
What is the difference between native and bridged USDC?
Native USDC is minted by Circle on that chain and can be redeemed with Circle. Bridged USDC, often labelled USDC.e, is minted by a bridge against USDC locked on another chain, and its backing depends on that bridge. Both can trade at a dollar, but they are different tokens.
Why do stablecoin decimals differ between chains?
Each deployment sets its own decimals. USDT and USDC use six on most chains, but some deployments, such as the Binance-Peg versions on BNB Chain, use eighteen. Sending an amount without checking decimals can move a very different amount than intended.
What is USDT0?
A version of Tether's USDT that moves between chains as an omnichain fungible token: USDT is locked on one chain and USDT0 is minted on another through the OFT standard. The table marks USDT0 deployments apart from USDT issued by Tether directly.
Can a stablecoin issuer freeze my tokens?
Most fiat-backed stablecoins can. Their contracts let the issuer block an address, and some can also destroy a blocked balance. The table shows whether each contract has these powers, and the blacklist tracker shows when they are used.
- Bridged token
- A copy of a token minted on one chain by a bridge, backed by the original locked on another chain.
- CCTP
- Circle's cross-chain transfer protocol, which burns USDC on one chain and mints it natively on another.
- OFT
- Omnichain fungible token, a LayerZero standard for tokens that move between chains by locking or burning on one and minting on another.
Related
More apps like this.
USDT Blacklist Tracker: Frozen USDT and USDC Wallets
Check whether an address is frozen by Tether or Circle, and follow how much USDT and USDC the issuers freeze, unfreeze and destroy.
Multi-chainEthereumTronUSDT vs USDC Supply by Chain
Where USDT and USDC each circulate chain by chain, and how the gap between Tether's and Circle's dollar coins changes over time.
Multi-chainEthereumTron+4Token Safety Check: Mint, Blacklist and Owner Powers
The powers a token contract still keeps, from minting and blacklisting to pausing, fee changes and upgrades, read from the contract.
Multi-chainEVM Chain List: Chain IDs, Native Tokens and RPC Support
EVM chains with their chain ID, native gas token, type, stack and settlement layer, plus the RPC methods their public endpoints answer.
Multi-chainEthereumBase+21Stablecoin Market Cap and Total Supply
Total stablecoin supply across chains, day by day, with its distance from the all-time high and the coins and chains behind it.
Multi-chainEthereumTron+4Build Stablecoin Contract Addresses: USDT, USDC and More by Chain on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.