Market cap
DIA price
Total supply
Holders
Withhelda chain leg dropped out of this read
The last read of Sei failed. This total is withheld because a chain leg dropped out of the read.
9,133,922holders
What the top-10 is
Shares of the same supply as Top-10, from public address labels covering 62.3% of the top-10 balance. Exchange custody is one address holding for many end holders. Unattributed means unlabelled, not self-custodied.
Measured on Ethereum. Shares are of the Ethereum supply, not the multi-chain total.
Market data · CoinGecko
Market data · CoinGecko
Circulating supply · DeFiLlama
Aggregator figure, not a contract read. DIA’s own onchain supply is the separate series below.
Percentage change in USDC's circulating supply as reported by DeFiLlama, measured against that source's own past. It is not a change in the onchain supply above, which DIA reads from the contracts directly and which is a different measurement of the same coin. A dash means the map has no reading close enough to the start of the window, a stretch inside it where supply was not reported at all, or a starting figure too small for a percentage to describe. Hover a dash for which.
10 of the 15 chains DIA holds a verified USDC contract on carry a deployment date and are plotted here. The other 5 were verified without one and are left off the curve rather than dated to the day DIA read them.
$3.72B
deployed across 46 markets on 16 protocols
Lower bound: USDC's balance inside lending markets DIA reads on-chain directly. Excludes DEX liquidity, CDP collateral, and any market on a chain or protocol DIA does not yet track. The share above is measured against a partial onchain supply figure — DIA has not yet read Sei.
DIA price
$0.9998
Peg deviation
-2 bps
Peg currency
USD
Launched
Primary use
—
Last snapshot
Sat, Sep 5 UTC
USDC is a US dollar stablecoin issued and redeemed by Circle Internet Financial, LLC and Circle Internet Financial Europe SAS, both subsidiaries of Circle Internet Group, Inc. Circle describes it as "a digital dollar backed 100% by highly liquid cash and cash-equivalent assets" and redeemable 1:1 for US dollars.
Where the reserve sits
The reserve sits in two places. The majority is held in the Circle Reserve Fund, a government money market fund registered under Rule 2a-7 of the Investment Company Act of 1940. Circle Internet Financial, LLC owns 100% of the equity interests in that fund, held on behalf of USDC holders. The remainder sits in segregated accounts at regulated financial institutions, unencumbered and separated from Circle's general corporate funds.
What Circle publishes
Circle publishes a monthly USDC Reserve Report with an accompanying Independent Accountants' Report. Circle's transparency page states that "a Big Four accounting firm provides monthly third-party assurance" and separately names Deloitte & Touche LLP as Circle's independent auditor since fiscal 2022. The attesting firm for the monthly reserve reports is not named in the extractable text of those reports.
The monthly report is an examination engagement, not an audit of Circle's financial statements. An examination gives an opinion on one narrow management assertion about the reserve, at the report dates.
What is not stated here
The reserve figures themselves are published as PDF examination reports that were not machine-readable at source for this page, so no circulation total, reserve total, Treasury holding, repurchase agreement balance or bank cash balance is stated here. Readers who need those numbers should open the monthly report directly from Circle's transparency page.
What Circle does not disclose
Circle does not name which banks hold the segregated cash portion of the reserve. The overnight repurchase agreement line names no counterparties.
In the EEA, USDC is issued by Circle Internet Financial Europe SAS. It is licensed by the Autorité de contrôle prudentiel et de résolution as an electronic money institution under ACPR register number 17788.
The MiCA redemption policy gives holders "a right of redemption of their Circle Coins at any time and at par value," subject to eligibility criteria. Circle states the redemption process should take no more than five business days once verifications are complete. Redemption is conditional on identity verification, transaction monitoring and asset freeze checks. Third party bank and conversion fees can apply, and Circle France disclaims responsibility for them.
Sources: Circle Europe MiCA Redemption Policy
The freeze function
USDC carries an issuer freeze function. Circle can restrict a holder's balance from access to comply with a law, regulation or legal order, and the monthly reserve report discloses the restricted amount as Access Denied Tokens. A holder's balance is contingent on Circle not being ordered to freeze it.
Contract supply overstates backed supply
Circle deducts Tokens Allowed But Not Issued, Access Denied Tokens and Circle Gateway pending burns before arriving at circulation for reserve purposes. Anyone summing raw contract totals across chains will overstate the backed float.
Repo exposure inside the reserve
The reserve is not purely Treasury bills. A material share sits in overnight repurchase agreements. That is exposure to the repo counterparty chain, mitigated by overcollateralization.
Redemption runs through Circle
Redemption at par runs through Circle, not through the chain. Anyone without a Circle Mint relationship exits through secondary markets, where the price can trade away from $1 regardless of reserve adequacy.
Sources: Circle Transparency and Stability page, Circle Europe MiCA Redemption Policy
The Global Stablecoin Map reads USDC token supply and market price on seven chains: Ethereum, Solana, Base, Arbitrum, Polygon, Avalanche and Optimism. Circle approves USDC issuance and redemption on more chains than those seven, so the on-chain figure shown here is a subset. Treat the coverage as a large majority of circulating USDC, not the full total. The stablecoin explorer shows that read next to every other tracked coin.
What the map cannot see
What is read on chain is contract supply and traded price. The reserve is off chain. No on-chain read can confirm the Circle Reserve Fund balance or the segregated bank cash. That link runs through the monthly examination report and nowhere else.
The Access Denied Tokens and Tokens Allowed But Not Issued adjustments that Circle applies to reach its circulation figure are also not derivable from raw contract supply, so an on-chain supply read will sit above Circle's stated circulation. Circle's other tracked token, USYC, is a fund interest and is covered separately.
USDC is issued and redeemed by Circle Internet Financial, LLC and Circle Internet Financial Europe SAS, both subsidiaries of Circle Internet Group, Inc.
The majority of the reserve sits in the Circle Reserve Fund, a Rule 2a-7 government money market fund. The remainder sits in segregated accounts at regulated financial institutions.
Circle publishes a monthly USDC Reserve Report with an Independent Accountants' Report. It is an examination engagement giving an opinion on one management assertion about the reserve. It is not an audit of Circle's financial statements.
Yes. Circle can restrict USDC from holder access to comply with a law, regulation or legal order, and discloses the restricted amount as Access Denied Tokens in its monthly reserve report.
In the EEA, USDC is issued by Circle Internet Financial Europe SAS, licensed by the French ACPR as an electronic money institution under register number 17788.
0xaf88d065…268e5831Explorer ↗0xb97ef9ef…d9c48a6eExplorer ↗0x833589fc…bda02913Explorer ↗0xceba9300…8b32118cExplorer ↗0x3d7f2c47…49999d2dExplorer ↗0xA0b86991…3606eB48Explorer ↗0xb88339cb…32ba630fExplorer ↗0x2d270e68…2161eaedExplorer ↗0x0b2c639c…d097ff85Explorer ↗0x3c499c54…3d5c3359Explorer ↗0xe15fc38f…2bf42392Explorer ↗EPjFWdd5Au…ZwyTDt1vExplorer ↗0x29219dd4…d4038894Explorer ↗0x078d782b…0ef57ad6Explorer ↗0x79a02482…b4cd24d1Explorer ↗0x1d17cbcf…a16538d4Explorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0xaf88d065…268e5831blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0xb97ef9ef…d9c48a6eblacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x833589fc…bda02913blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0xceba9300…8b32118cblacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x3d7f2c47…49999d2dblacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0xa0b86991…3606eb48blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0xb88339cb…32ba630fblacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x2d270e68…2161eaedblacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x0b2c639c…d097ff85blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x3c499c54…3d5c3359blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0xe15fc38f…2bf42392blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacyEPjFWdd5Au…ZwyTDt1vfreezeAuthoritymintAuthority0x29219dd4…d4038894blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x078d782b…0ef57ad6blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x79a02482…b4cd24d1blacklist(address), unBlacklist(address) +1paused()mint(address,uint256), configureMinter(address,uint256) +1zeppelinos-legacy0x1d17cbcf…a16538d4zeppelinos-legacyRead from the deployed contract. “Not determined” means the contract’s full function set could not be enumerated, not that the capability is absent: a bytecode scan can confirm that a function exists and can never prove that one does not.