USDC transfers are tracked through network-specific contract or native-asset records, with addresses, amounts, timestamps, fees, and route interactions providing the core evidence.
Contract identity is essential
Circle publishes network-specific identifiers for supported USDC representations. Researchers and users should verify the exact contract rather than rely on the symbol.
Follow the chain’s model
EVM networks use account transactions and token logs, while Solana uses signatures and token accounts. Each representation must be followed with its native data tools.
Cross-chain USDC
Bridges and transfer systems can create burn, mint, message, or liquidity records. Amount and timing correlation may complement explicit identifiers.
Privacy remains route-specific
A private route can reduce a direct wallet association where offered without hiding USDC transfers on either ledger.
How to read the evidence
USDC is represented by network-specific contracts or identifiers, so analysis must follow the exact source and destination records. Base uses EVM transactions and logs; Solana uses signatures and token accounts. Cross-chain mechanisms can add messages, burns, mints, or liquidity delivery. Similar output values help research but do not prove a match without supporting route evidence.