A USDT or USDC Polygon explorer check takes three facts: the transaction status, the recipient, and — the part most people skip — the token contract address. On Polygon PoS, real USDT is 0xc2132D05D31c914a87C6611C10748AEb04B58e8F, native USDC is 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359, and bridged USDC.e is 0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174. Anything else wearing those names is not the real thing.
Stablecoins are now the main reason people use Polygon. Payments, payroll, remittances, merchant checkouts — much of it moves in USDT and USDC at fees of a fraction of a cent. That popularity also makes stablecoins the favourite disguise for scams. This guide is the checklist our team uses when we verify a stablecoin transfer, with every address checked against Blockscout and PolygonScan on 25 September 2026.
Quick answer
Open the transaction in a Polygon explorer, confirm Success, then check the token contract in the transfer line, not just the symbol. Compare it with the addresses below. Fees are paid in POL. If an exchange deposit is missing, confirm you used the Polygon network and the exact token version the exchange supports.
Official USDT and USDC contract addresses on Polygon
Bookmark this table or copy it somewhere safe. All three tokens use 6 decimals, which means a raw on-chain value of 1000000 equals exactly 1 USDT or 1 USDC.
| Token | Contract address | Issuer |
|---|---|---|
| USDT (USDT0) | 0xc2132D05D31c914a87C6611C10748AEb04B58e8F | Tether |
| USDC (native) | 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359 | Circle |
| USDC.e (bridged) | 0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174 | Bridged from Ethereum |
To give you a sense of scale: when we queried Blockscout on 25 September 2026, the USDT contract had about 6.3 million holders and native USDC about 4.2 million. Holder count is a reasonable sanity check, but — as you'll see below — not proof on its own. Always match the address character by character, or at least the first six and last six characters plus the explorer's token page. Official sources are Circle's USDC page and Tether's site, both of which list supported chains and contracts.
What is USDT0?
If your explorer shows "USDT0" at the familiar 0xc2132D…8e8F address, don't panic. USDT0 is Tether's omnichain version of USDT, and on Polygon the existing USDT contract now carries that name in some explorers. Blockscout labelled it USDT0 in our checks; other explorers and many wallets still say USDT or "(PoS) Tether USD". What matters is the address, which did not change. Exchanges generally list it simply as USDT on the Polygon network.
Native USDC vs USDC.e: which one do you have?
This is the question we're asked most about Polygon stablecoins. Before Circle issued USDC directly on Polygon, the only USDC on the chain was a bridged token — USDC locked on Ethereum and represented on Polygon by a separate contract. When Circle launched native USDC on Polygon PoS (in October 2023), the old token was renamed USDC.e to avoid confusion.
| Native USDC | USDC.e | |
|---|---|---|
| Issued by | Circle, directly on Polygon | PoS bridge from Ethereum |
| Explorer symbol | USDC | USDC.E or USDC.e |
| Exchange deposits | Widely supported | Often not credited |
| Redeemable with Circle | Yes | Only after bridging back |
Both are worth about a dollar and both are legitimate tokens. The practical difference is where you can use them. Many centralized exchanges only credit native USDC on Polygon; sending USDC.e to such an address can leave funds in limbo until support manually recovers them — if they do at all. DeFi apps usually support both, and you can swap one for the other on most Polygon DEXs for a small spread.
To check which one you hold, open your address in our Polygon wallet explorer and look at the token list: the contract behind each balance is one click away. Our wallet tracking guide explains that view in more detail.
Spotting fake USDT, fake USDC and address poisoning
Creating a token called "USDT" on Polygon costs less than a cent. Scammers do it constantly. When we searched Blockscout for "USDT" on 25 September 2026, the real contract came first — but right behind it were several other contracts with USDT in their symbol, one of them a spam token whose name advertised "5000$ rewards" and a website, "held" by over 500,000 addresses it had simply airdropped itself to. A big holder count means nothing if the tokens were sprayed out for free.
Red flags we look for:
- Wrong contract address. Everything else is secondary.
- A website or "claim" text in the token name. Legitimate stablecoins never do this.
- Balances you didn't expect. Free stablecoins don't exist. An unexplained 5,000 USDT is almost certainly a worthless look-alike.
- Missing price. Explorers usually show a USD value for real USDT and USDC. A "USDT" with no price or a nonsense price is fake.
Address poisoning
The subtler trick is address poisoning. An attacker generates an address that begins and ends with the same characters as one you use — say 0x7a3F…91cE — and sends you a zero-value or tiny transfer from it. Now that look-alike sits in your transaction history. Next time you copy "the usual address" from history, you might grab theirs.
Explorers try to help: PolygonScan hides many zero-value token transfers by default and flags suspicious tokens, and Blockscout marks token reputation. But the only reliable defence is habit. Copy recipient addresses from your address book, the recipient's own invoice, or a QR code — never from your transaction list — and compare more than the first and last four characters.
How to confirm a USDT or USDC payment on Polygon
Whether you're a merchant waiting for a customer or a freelancer waiting for a client, the check is the same. Ask for the transaction hash (a 66-character string starting with 0x), then:
- Paste the hash into an explorer. Use our free Polygon transaction lookup or PolygonScan. You should see Success, the block number and a timestamp in UTC.
- Open the token transfer line. For a stablecoin payment the POL "Value" is usually 0 — the money is in the ERC-20 transfer underneath. Check the token contract matches the table above.
- Check the recipient and amount. The "To" in the token transfer should be your address, and the amount should match the invoice. The transaction's top-level "To" is often the token contract itself — that's normal.
- Confirm finality. Since Polygon's Heimdall v2 upgrade, blocks are final in about five seconds. A few confirmations are plenty for everyday payments.
- Save proof. Our tool's Share button creates a link, a QR code or a printable payment receipt you can attach to an invoice.
We go through proof-of-payment etiquette, screenshots versus links, and what to send an accountant in the dedicated guide to verifying a Polygon payment. One tip from experience: a screenshot of a wallet saying "sent" proves nothing. A transaction hash does.
Why your exchange deposit doesn't show up
A Polygon explorer says Success, the recipient is your exchange deposit address, and yet your exchange balance hasn't moved. In our experience the cause is one of these, in roughly this order of frequency:
- Wrong network. The same
0x…address format is used on Ethereum, BNB Chain, Arbitrum and Polygon. If the exchange generated that address for USDT on Ethereum and you sent on Polygon, the exchange's Ethereum deposit system never sees it. Most exchanges can recover this, but it can take days and sometimes costs a fee. - Wrong token version. You sent USDC.e and the exchange only credits native USDC — or a bridged variant from another project.
- Deposits suspended. Exchanges pause Polygon deposits during upgrades or maintenance. Check their status page.
- Minimum deposit. Amounts below the exchange's minimum may not be credited automatically.
- Missing memo or tag. Rare on Polygon, but some platforms still use them.
Before contacting support, collect the transaction hash and a link to it on an explorer. That's the first thing they'll ask for. And before you send next time, look at the withdrawal or deposit screen on both sides and make sure both say Polygon (sometimes "Polygon PoS" or "MATIC network" on older interfaces). If you still need USDC or POL on Polygon, buy it on a regulated exchange that holds licences in several jurisdictions and lets you withdraw directly to the Polygon network — check the withdrawal network before you confirm.
Moving stablecoins from Ethereum to Polygon yourself is a different process with its own waiting times; our Polygon bridge explorer guide explains how to track a bridge transfer on both chains.
Token approvals: the stablecoin risk people forget
When you use a DEX, a lending app or an NFT marketplace with your USDT or USDC, you usually sign an approval first. It lets a smart contract move your tokens — sometimes up to an "unlimited" amount. Approvals don't expire on their own. If that contract is later exploited, or if you approved a malicious one on a phishing site, your stablecoins can be drained without you signing anything new.
Explorers let you audit this. PolygonScan has a token approval checker where you paste your address, see every spender with an active allowance and revoke those you don't need (revoking costs a tiny POL fee because it's a transaction). Blockscout shows approvals in the address view as well.
Revoke often
Once a month, clear approvals for apps you no longer use, especially unlimited ones on USDT and USDC.
Approve exact amounts
Most wallets let you edit the spending cap. Approve the amount you're about to use, not "unlimited".
Which explorer is best for stablecoin checks?
All major Polygon explorers show ERC-20 transfers correctly, so any of them will confirm a USDT payment. PolygonScan is the most familiar and has the approval checker built in; Blockscout shows token reputation and has a free API if you want to automate payment checks; our own tool adds a shareable receipt without sign-up. We compare the field in our best Polygon explorers ranking, and our PolygonScan review covers its token pages in depth.
Whichever you use, the rule stays the same: the contract address is the truth. Symbols, logos, holder counts and friendly names can all be faked. Six characters at the start and six at the end, checked against the table on this page, take ten seconds and stop almost every stablecoin scam we've seen.