USDT tracking begins with the chain and contract: ERC-20 activity is followed through EVM accounts and events, while TRC-20 activity is available through TRON account and transaction history.
The ticker is not the ledger
USDT exists on multiple networks. Each representation has its own contract, address format, fee system, and explorer data.
Ethereum-style records
An ERC-20 transfer can expose sender, recipient, amount, token contract, transaction hash, gas payer, and related approvals.
TRON records
TRC-20 history can be queried by account and contract, while transactions contain sender signatures, contract content, timestamps, and resource use.
Cross-chain correlation
A route connecting representations may be analyzed through known infrastructure, output after fees, timing, and destination behavior.
How to read the evidence
USDT analysis begins by naming the network and contract. TRC-20 and ERC-20 histories use different resource and execution models, yet both are publicly queryable. Cross-chain routes may exchange representations rather than move one token object between ledgers. Check the provider, source contract, destination representation, and public endpoint records before describing the route’s privacy effect.