USDT is a contract, not a coin
USDT does not move the way the native asset of a network moves. On Ethereum it is an ERC-20 token contract; on Tron it is a TRC-20 contract. When someone sends you USDT, no balance physically travels — the token contract records a new pair of balance entries and emits a Transfer event containing the sender, the recipient and the amount.
This matters for tracing because a wallet's native balance (ETH or TRX) tells you almost nothing about its stablecoin activity. An address can hold six figures in USDT while showing a native balance of a few pounds' worth of gas. Any trace that looks only at native transfers will miss the entire case.
Building the transfer graph
A trace starts from a known point: the address you sent funds to, or a transaction hash from your own wallet or exchange withdrawal history. From there the work is to follow Transfer events outward, hop by hop, and record how the value splits and recombines.
- Each hop is a directed edge: source address, destination address, amount, timestamp, transaction hash.
- Value is usually split across several outputs at the first or second hop to make manual following harder.
- Small amounts are often peeled off deliberately as noise; the bulk of value tends to stay on one dominant path.
- Timing is evidence in itself — funds moving within seconds of arrival, repeatedly, indicate automated forwarding rather than a human counterparty.
What Tron does differently
Tron's low fees change fraud behaviour. Because a TRC-20 transfer costs a fraction of the equivalent Ethereum transaction, operators can afford far more hops, far more intermediate addresses and far more decoy transfers. A Tron trace often has three to five times the hop count of an equivalent Ethereum trace for the same loss.
Tron also uses an energy and bandwidth model rather than simple gas payments, and accounts are frequently funded by a single sponsor address. That sponsor is often more informative than the transfer graph itself: one address quietly paying activation costs for dozens of receiving wallets is a strong clustering signal.
Where a trace realistically ends
Every honest trace ends at one of a small number of terminal points, and knowing which one you have reached is the most useful output of the work.
- A deposit address at a centralised service. The on-chain trail stops here; anything further is held by that service and only released to law enforcement or under legal process.
- A bridge or cross-chain swap. The trail continues on another network, and continuity has to be evidenced by amount and timing correlation rather than by a single transaction.
- A mixer or privacy protocol. Statistical association may remain possible, but deterministic linkage usually does not, and we say so plainly rather than dressing it up.
- A dormant address. Funds are simply sitting still. This is more common than people expect and is worth documenting, because the position can change months later.
What the public ledger does not tell you
The ledger records addresses, not people. No amount of tracing reveals a name, a passport or a location by itself. Attribution comes from linking an address to off-chain information — a published deposit address, a service's known address set, a disclosure made under legal process — and that step is either supported by evidence or it is speculation.
This is the point where recovery scams and genuine forensics diverge. Anyone promising to identify the individual behind an address purely from on-chain data, or to reverse a confirmed transaction, is describing something the technology does not permit.
What a usable trace report contains
- The starting point and how it was established from your own records.
- The full hop path with transaction hashes, so any third party can verify each step independently.
- Amounts at each hop, including where value was split, and what proportion of the original loss each branch carries.
- The terminal classification for each branch, with the reasoning stated.
- A clear statement of confidence, including which links are deterministic and which are inferred.
Common questions
- Can a USDT transfer be reversed?
- No. A confirmed TRC-20 or ERC-20 transfer is final and cannot be reversed by anyone, including the token issuer's ordinary operations. Tracing establishes where value went; it does not undo the transfer.
- Does tracing tell you who owns an address?
- Not on its own. On-chain data identifies addresses and their relationships. Linking an address to a real identity requires off-chain information, usually held by a regulated service and released only under legal process.
- How far can funds be followed?
- Until they reach a terminal point — a centralised service deposit address, a bridge, a privacy protocol, or a dormant address. The number of hops varies from two to several hundred, and low-fee networks like Tron tend towards the higher end.
Have a case you want reviewed?
We scope at intake and tell you honestly whether the on-chain data supports a traceable case.