Stolen USDT Was Swapped: How to Document the Next Transaction

To trace stolen USDT after a swap, follow the output asset and its recipient, not just the original USDT token page. One transaction can contain several token transfers, pool interactions and fees. This guide uses an explicitly fictional Ethereum example to show how to document that step. For the starting transfer see how to trace USDT; complex routes belong in blockchain analytics.
A transaction hash is a container for several actions
In an Ethereum transaction, the top-level destination may be a router contract rather than the final recipient. The token transfer events show individual movements emitted by token contracts. Etherscan separates transaction information and event logs; a single hash can therefore appear beside several entries in your worksheet.
Record the exact token contract as well as the ticker. A token called USDT is not necessarily the issuer's USDT. Identify the network before choosing an explorer, and use the issuer's supported-protocol information to check the contract. Do not apply this Ethereum example unchanged to TRON or another chain.
An approval grants permission; it does not by itself show that the exchange of assets happened. Look for a successful execution and corresponding asset movements. A convenient 'Swap' label is a starting point for inspection, not a substitute for reading the underlying records.
Read the input, the pool and the actual output recipient
Start at the address that received the reported stolen transfer. Locate the candidate swap and record its status, block time and hash. Within that transaction, identify which contract emitted each relevant transfer event, which addresses sent and received assets, and the amounts after applying the token's decimals.
The Uniswap v3 pool interface documents a Swap event with a recipient and signed changes in the two token balances. That helps interpret a pool interaction, but the pool recipient may still be another contract in a longer route. Continue through the transaction's relevant transfers until you identify the final output destination or a point you cannot resolve.
| Observation | Record | Do not conclude |
|---|---|---|
| USDT enters a router or pool | Token contract, amount, sender, receiver, event | The router operator stole the funds |
| A pool emits a swap event | Pool, tokens, event and recipient | This is necessarily the entire route |
| An output token reaches an address | Contract, amount and recipient | The address belongs to the same person without further evidence |
| Several inputs are combined | All relevant inflows and uncertainty | Every output unit came from the victim |
Educational example and first-step checklist
This example is invented solely to demonstrate record keeping. T1, T2, A, B and C are labels, not real transaction hashes or addresses; 0.40 WETH is an illustrative output, not a market quotation.
At T1, a victim reports an unauthorised transfer of 1,000 USDT to A. At T2, A exchanges 1,000 USDT and the transaction records 0.40 WETH reaching B through router C. The next item to inspect is B's WETH activity, while retaining the reference to T2. The original theft allegation still needs the victim's evidence; the swap record alone does not establish it.
- Preserve T1 and the evidence connecting it to the reported loss.
- Open T2 in the correct explorer and confirm successful execution.
- List USDT input events and their emitting contract.
- Record swap events and output transfers, including intermediary contracts.
- Identify the output token, amount and final recipient supported by those records.
- Mark unresolved routing or mixed balances before following further transactions.
Give each relevant event its own row and event/log index where available. If T2 contains three pool interactions, do not sum their input values as three separate losses. The reported loss and the volume of subsequent activity are different totals.
Where the trail becomes uncertain
A swap does not automatically erase the public trail. It changes what you follow. However, mixed balances, aggregators, bridges and exchange custody can prevent a simple one-to-one claim about where a victim's value went. State the observed links and the assumptions used to relate them.
If the next step is an exchange deposit, retain the basis and date of any service attribution. The scammer-wallet tracing guide explains why a public address is not a person's identity. Do not contact unrelated liquidity providers as if they controlled the suspect's wallet.
For an assessment, send the original loss transaction, candidate swap hash, network and worksheet with uncertainties. The useful deliverable is a reproducible route and identification of missing evidence; tracing alone cannot freeze or return assets.
Risks and limitations
- The example is fictional and is not evidence of a theft or a real trading rate.
- A token ticker or explorer label alone is insufficient to identify an asset or route.
- Combined balances and multi-hop swaps can limit attribution of a particular victim's value.
- A swap recipient is a public address, not proof of a person's identity.
- A transaction map does not guarantee freezing or recovery.