How ETH and ERC-20 Tokens Are Tracked: Transfers, Contracts, and Events
In Ethereum, it's important to analyze not only regular ETH transfers but also token events, contract calls, DEXs, and bridges.
A public blockchain provides many facts, but it doesn't label them with ready-made conclusions. In Ethereum, it's important to analyze not only regular ETH transfers but also token events, contract calls, DEXs, and bridges. A good analysis starts exactly at this boundary.
The main thing to know right away: A good investigation must be reproducible: every significant conclusion has a tx hash, an attribution source, and a clear explanation of how that conclusion was reached.
What is visible on the blockchain
In Ethereum, you need to consider more than just regular ETH transfers. ERC-20 assets move through contract events, and a single transaction can include a DEX, bridge, swap, and multiple internal actions.
In Ethereum, it's important to analyze not only regular ETH transfers but also token events, contract calls, DEXs, and bridges. At the same time, any entity name — exchange, bridge, mixer, swap service — must be tied to an attribution source. The blockchain itself does not store labels with owners' names.
How to break down the task step by step
Open not only the regular transfers tab but also token transfers, logs/events, and contract interactions. For an investigation, it's important to understand the economic result of the call, not just the to field.
- Start with a specific starting point: a tx hash or a verified address.
- Clarify the network, asset, amount, and time interval.
- Build the sequence of operations and note transitions between networks, DEXs, bridges, and centralized services.
- Separate on-chain fact from external attribution: a label like "exchange" or "swap service" must have a source.
- Formulate the conclusion so that another specialist can re-verify the route.
What source data is needed
For this specific topic, it's especially useful to save: Ethereum tx hash, token contract and Transfer events/contract calls related to the movement.
For an initial review, prepare the data in a single message or file — this reduces the risk of losing an important detail:
- tx hash
- addresses
- network and asset
- time interval
- brief context: what exactly needs to be established
Where mistakes are most common
- Don't assume an address is automatically an identified individual.
- Don't present a probabilistic link or heuristic as a proven fact.
- Don't substitute an investigation with a single AML risk score.
Important: an analytical link must have a confidence level. Where the data only allows a hypothesis, this must be stated explicitly.
When a full review is needed
If the answer will be used not only "for yourself" but for a lawyer, a company, an exchange, or further action, it's better to document the route with a table, a graph, and attribution sources. This makes the result understandable and verifiable.
Frequently asked questions
Does the "to" field always show the final recipient of the token?
No. When interacting with a smart contract, the to field may point to the contract, while the actual token movement is visible in events and internal actions.
Is wallet access needed?
For analyzing public transactions, usually not. A seed phrase and private keys are not needed.
What is the result of an investigation?
Depending on the task — a route, a transaction table, a graph, service attribution, conclusions, and explicitly stated limitations.
In short
In Ethereum, it's important to analyze not only regular ETH transfers but also token events, contract calls, DEXs, and bridges. A useful result is not just a picture, but a verifiable chain of facts with clear sources and limitations.
Need a transaction chain review?
For an initial assessment, a tx hash, network, and a short timeline are usually enough.
Submit tx hash