What this page tracks
This USDC whale tracker focuses on large USD Coin transfers across the supported chains and venues where USDC is used as a regulated stablecoin liquidity layer. The table is filtered for USDC, so it does not mix USDC movement with BTC, ETH, USDT, or other assets. Each row is meant to answer a narrow set of questions: which network carried the transfer, how much value moved, which side of the route has a known label, and does the movement look like an exchange flow, treasury operation, mint, burn, bridge route, custody movement, or ordinary wallet transfer?
USDC needs its own reading model because stablecoin movement often describes liquidity routing rather than direct market intent. A large USDC transfer into a labeled exchange can show that dollar liquidity reached a venue, but it does not prove that the sender bought or sold a crypto asset. A large outflow can show USDC leaving exchange infrastructure, but the destination may be a custody wallet, an institutional account, a treasury address, an OTC route, a bridge, or another operational wallet. The network matters because the same asset can move through different settlement paths depending on the chain, venue, and wallet cluster involved.
OnChainFlows treats USDC whale tracking as blockchain analytics. The useful part is the context around the transaction: sender, receiver, entity labels, transaction hash, token amount, USD value, flow type, network, and links into the wider dashboard. Mint and burn events are kept separate from whale wallet behavior because they describe supply-side activity before funds move through the market. Bridge and cross-chain transfers also need their own bucket. They may move liquidity between networks or venues without showing a simple change in owner intent.