USDT and USDC Contract Addresses. Every Chain, Verified, With the Explorer Link to Prove It.

The One Rule

A stablecoin is a contract. "USDT" is just the three letters the contract was given when it was deployed, and anyone can deploy a contract and give it those three letters. On Tron alone there are tens of thousands of tokens named USDT. One of them is Tether's. The rest are somebody else's, and a lot of them exist specifically so that you will confuse the two.

So the rule is simple. The name proves nothing. The address proves everything. If the address matches the one Tether or Circle publishes, it is real. If it does not, it is not, however convincing the logo looks in your wallet.

This page is the list of addresses that match, chain by chain, copied from the issuers' own pages and cross-checked against the block explorers. Each row links to the explorer so you can look at the live contract instead of trusting me. Where I could not confirm a full address from an official source, the row says "see explorer" and links you to the place to check it. I would rather leave a cell blank than put a wrong address on a page that people will copy.

Check an Address Now

Paste any contract address, mint or asset ID and the checker tells you whether it is an issuer-published USDT or USDC contract, on which chain, with what status and decimals. For Tron and Ethereum it also reads the live contract and shows you what the chain itself says the token is called. Nothing is sent to us; the list is in the page. The full tool has its own page if you want to bookmark it.

USDT: Native Tether Contracts

These are the chains where Tether itself issues USDT. Tether's supported-protocols page and its transparency report are the source of truth; Bitfinex's transport-protocols article lists the same set and is where the deprecations get announced first. Tron carries the largest supply, Ethereum the second, and together they hold the large majority of all USDT in circulation (Etherscan alone shows 84 billion on Ethereum as of November 2026).

Everything we have measured about the Tron contract, from transfer counts to freezes, lives on the Tron USDT statistics hub. Two things to notice here. First, Tron, Ethereum, Solana, TON and Avalanche are all six decimals, so 1 USDT is always 1,000,000 base units and amounts move between those chains without a conversion. Second, several chains identify the token by something other than an address: an asset ID on Polkadot (1984), an account name on NEAR, a coin type on Aptos. A wallet or an API will usually ask for that identifier in the field labelled "contract address". It is the same idea.

USDT0: The Upgraded Chains

In 2025 Tether started moving its layer-2 and newer-chain presence onto USDT0, an omnichain token built on LayerZero and backed by USDT locked on Ethereum. On Arbitrum and Polygon the existing USDT contracts were upgraded in place, so the address you already had kept working and the token name changed to USD₮0. On chains Tether did not previously serve, USDT0 is the only USDT there is, and the list has grown fast: by November 2026 it includes Hedera (March 2026), Stellar (September 2026) and IOTA, with Cardano in rollout.

This matters for one practical reason. Older guides and token lists still call the Arbitrum and Polygon tokens "bridged USDT". They are not any more. The address is the same, the backing is now Tether's own, and the token moves between USDT0 chains natively. Several USDT0 deployments also share one address across chains (0x779D…3736 on Berachain, Mantle, Rootstock, Stable and X Layer, for instance), which is convenient and also the one case where "same address, different chain" is not a red flag.

USDT: Bridged by the Chain

This is the table most lists leave out, and it is where the confusion lives. On Base, Optimism, Gnosis, Linea, Scroll, Cronos, zkSync, opBNB and Sui there is a token called USDT that Tether never deployed. The chain's own canonical bridge created it by locking real USDT on Ethereum and minting a copy. It is redeemable through that bridge, not through Tether, and it carries the bridge's risk on top of Tether's. Most of the time that is fine. The point is to know which one you hold.

Some rows say "legacy": a bridged token that a native or USDT0 contract has since replaced on the same chain. Avalanche's USDT.e, NEAR's USDT.e and Optimism's standard-bridge USDT are the big ones. They still trade and still have holders, and they are not the token the issuer points to.

USDT: Pegged and Legacy

This table is the one that saves people money. The BNB Chain row in particular: the token almost everyone calls "USDT BEP-20" is not issued by Tether. It is a Binance product, backed by USDT that Binance holds elsewhere, with 18 decimals instead of 6. That is fine if you trust Binance, and most people do, but it is a different thing from holding Tether's own liability, and software that assumes 6 decimals will display it wrong by a factor of a trillion.

The legacy rows are the five chains Tether stopped issuing and redeeming on from 1 September 2025: Omni, Algorand, EOS, Bitcoin Cash SLP and Kusama. Tether originally planned to freeze those contracts and, after pushback from the ecosystems, decided not to. So the tokens still move, but nobody stands behind them and most exchanges will not take them. No new guide should send you there.

Chains With No USDT

The most useful row on a reference page is sometimes the empty one. People search for "USDT on Cardano" and "USDT on XRP" every day, and the honest answer is that Tether does not issue there, or does not yet. Anything with the USDT name on those chains is either a third-party wrapper or a copy. The two Bitcoin rows are the ones to watch: Tether has announced native USDT on Bitcoin twice, once over Lightning with Lightning Labs in January 2025 and once over the RGB protocol for 2026. Neither had a public asset ID you could verify when this page was last updated. When one appears it goes in the native table with a link.

USDC: Native Circle Contracts

Circle publishes a single page of every chain where it issues USDC natively, and this table mirrors it row for row. Native means Circle minted it and Circle will redeem it. The list is longer than Tether's because Circle's strategy has been to deploy on as many chains as possible, including several (Arc, Codex, EDGE, Pharos, Plume) that most readers will never touch. They are here because the point of this page is completeness, and because the chain you have never heard of is exactly where a fake address does the most damage.

USDC: Bridged, Pegged, Discontinued

The USDC.e problem. On Arbitrum, Polygon, Optimism and ZKsync there are two tokens called USDC. The native one is Circle's. The other, now labelled USDC.e, was created by the chain's bridge in the years before Circle deployed natively, and is backed by USDC that the bridge holds on Ethereum. They have different addresses, they are not the same token, and a growing list of exchanges will reject deposits of the bridged one. If you are choosing, choose native. If you already hold USDC.e, most chains have a one-click swap and the rate is one to one.

And Tron. Circle issued USDC on Tron from 2021, stopped minting in February 2024 and ended its support entirely in February 2025. The contract is still on the chain and the token still changes hands on some venues, but there is no longer an issuer behind it. On Tron, the dollar is USDT.

Decimals

A token's decimals setting is how many base units make one whole token. USDT and USDC use 6 almost everywhere, which means an on-chain balance of 1000000 is 1.00 USDT. It is why a Tron explorer shows transfer amounts as integers with six implied decimal places, and why our blacklist statistics divide every raw value by one million.

If you are writing code against these contracts, read decimals() from the contract rather than hard-coding 6. The BNB Chain tokens are the trap, and they are the ones a developer is least likely to test against first.

How to Verify an Address

Do not trust this page either. Trust the method. Three checks, in order, for any token on any chain.

How Fakes Work

I have watched enough of these to describe the pattern without describing a method. There are three families.

The name clone. A contract deployed with the symbol USDT, the Tether logo uploaded to a token list or a DEX, and liquidity seeded against TRX or ETH so it has a price. It gets sent to wallets in bulk, or listed on a small exchange, or passed off in a P2P deal. The address is different from Tether's, which is all you need to know.

The vanity match. An address generated to share the first few and last few characters of a real one, so a quick glance passes. Wallets that truncate addresses in the middle make this work. Explorer pages that show the full string defeat it. Compare the whole address or compare none of it.

The wrong network. Not a scam, just a mistake, and the most common loss of all: real USDT sent on a chain the recipient does not support. ERC-20 to a Tron deposit address, Binance-Peg to an exchange that only accepts Tether-issued, USDC.e to a venue that delisted it. The contract addresses on this page do not help you send. They help you check what you are about to receive is on the network you expect, which is the half of the problem people skip.

Adding the Token to a Wallet

Most wallets already know the native USDT and USDC on the big chains and show them automatically. You need the address when a wallet does not recognise a token, when you are on a newer chain, or when you want to be certain the one it shows is the real one. The fields are the same everywhere: network, contract address, symbol, decimals. The symbol and decimals usually fill themselves once the address is pasted. If the decimals field fills with something other than 6 on a chain in the native tables above, stop.

If you are on Tron and the reason you are here is that a transfer failed, it is almost never the address. It is Energy. The fee calculator shows what a USDT transfer costs today, and the no-Energy post explains why the chain burns your TRX when you have none. If you are choosing a wallet in the first place, the wallet comparison covers the four we would use, and if you move USDT for a desk, Energy for OTC desks is the page written for you.

Cite This Page

This list is maintained. I check it against Tether's and Circle's pages each quarter and whenever either issuer announces a new chain or a sunset, and the "last updated" date at the top changes when a row does. If you are a wallet, exchange, developer or writer who needs one URL to point people to, point them here, and tell me if a row is wrong. Corrections go in the same day.

One address per chain is real. Now you have all of them in one place, with the receipts.

Ping. Still here.

Sources: Circle, USDC contract addresses (all native USDC rows, copied verbatim) · Tether, supported protocols and Tether transparency (native USDT chains) · Bitfinex, Tether token transport protocols (supported and discontinued chains, Cosmos/Kava naming) · Etherscan (ERC-20 USDT, 6 decimals, holder count) · Tether news (Ethereum contract) · Kaia Foundation (Kaia USDT contract) · Eco (NEAR native vs bridged) · Pera Explorer (Algorand ASA 312769) · USDT0 deployments (Everdawn Labs), the USDT0 ecosystem pages (per-chain addresses for Stable, Mantle, X Layer, Monad, Morph, Tempo, Conflux, IOTA, Stellar, Celo), Hedera docs (USDT0 token 0.0.10282787), Goldsky (bridged USDT on Base, Optimism, Gnosis, Linea, Scroll, Avalanche USDT.e), Liquid docs (USDt asset ID, precision 8), Cointelegraph (Tether did not freeze the five legacy chains, Aug 2025), IOG (Cardano USDT0 rollout status), Crypto Briefing (USDT on Lightning not yet live), CoinGecko bridged USDT (Cronos, opBNB, zkSync, Polygon zkEVM, Aurora supply) and USDT0 on Polygon (upgrade in place) · Sei, USDT migration guide · Arbitrum docs and Request Finance (USDC.e addresses) · Circle (Tron discontinuation, 21 Feb 2024) · Kraken (USDC.e support ending) · DIA (cross-check of USDT chain list) · Datawallet and USDT Check (secondary cross-checks of EVM, Solana and TON addresses).