Check Which USDC Reached Your Arbitrum Wallet

On Arbitrum One, Circle’s native USDC contract is 0xaf88d065e77c8cC2239327C5EDb3A432268e5831. That address tells you whether a transfer reached you as Circle-issued USDC; the ticker and token name alone do not.

Arbitrum also has bridged USDC, commonly labeled USDC.e, at a different contract address: 0xFF970A61A04b1cA14834A43f5de4533eBDDB5CC8. Both tokens can appear as “USDC” in interfaces, but they are separate assets onchain and are not interchangeable at the contract level.

The network and route matter too: a token can move across chains through a bridge, or a routing service can swap and transfer assets in one flow. For a separate explanation of QuickSwap’s Ethereum-to-Solana routing, see the developer walkthrough.

How do you check which USDC arrived?

Open the transaction in an Arbitrum One block explorer and inspect its token transfers. The token contract address identifies the asset, while the transaction’s “To” address shows the recipient.

Use this sequence:

1. Find the transaction hash in your wallet’s activity or the sender’s transfer record, then open it in Arbiscan.
2. Confirm the transaction is on Arbitrum One and check that its status succeeded.
3. Look in the token transfer events for the amount and recipient, then open the token’s contract page.
4. Compare the contract address with Circle’s native USDC address above or the USDC.e address. Check every character; token names and symbols can be copied.

An ERC-20 transfer is recorded as an event emitted by the token contract. In the explorer, the contract address associated with that event is the key evidence. A successful transaction can include several token transfers, so match both the amount and your wallet address rather than relying on the first transfer shown.

Why are there two USDC tokens on Arbitrum?

USDC.e came from the canonical Ethereum-to-Arbitrum bridge, which locks tokens on Ethereum and creates corresponding bridged tokens on Arbitrum. Circle later issued native USDC directly on Arbitrum, with its own contract.

The two routes create different onchain assets, even though both aim to represent US dollars. A bridge or exchange may support one version and not the other, and an app can show the same short ticker for both. That is why the contract address matters when you deposit, trade, or withdraw.

Circle’s Cross-Chain Transfer Protocol (CCTP) uses a different model for supported transfers: it burns USDC on the source chain and mints native USDC on the destination chain. A transfer through the canonical bridge can instead result in USDC.e. The route’s name is useful context, but the destination transaction and contract tell you what actually arrived.

What should you check before using the token?

Check the contract at the point you plan to use the funds. A wallet balance confirms that a token is held at your address; it does not prove that a particular exchange, lending app, or payment service accepts that version.

• Contract: Match the full address to the token you intend to hold.
• Network: Confirm the explorer and wallet are set to Arbitrum One, not another Arbitrum network or Ethereum.
• Destination support: Check that the receiving service accepts native USDC or USDC.e before sending.

If you only see a ticker in your wallet, open the token details and compare its contract address. If the token is missing from the display, the explorer can still show the transfer; adding a token to a wallet’s display does not change what the contract is.

For most users starting a new transfer, native USDC is the clearer choice when the destination supports it: Circle issues it on Arbitrum, and its identity is easy to verify against the published contract. Keep USDC.e when you specifically need it for a service or route that supports that bridged version. In either case, verify the destination’s supported contract before moving funds.