Begin with the scope and the starting transactions
A tracing report should tell the reader which transactions were examined, on which networks and to what cut-off point. Without that scope, an apparently complete diagram may leave uncertainty about which payments or later movements were included.
Check the identifiers against the source material and distinguish the asset from its symbol. Similar labels can appear on different networks or contracts. Ask how the analyst treated internal transfers, fees and any conversion between assets, so totals in the report can be understood.
A useful report allows a reviewer to move from the summary back to the transaction records supporting it. The diagram is a navigation aid to that evidence.
Reference: Ethereum: transactions
Read observed links and inferred links differently
Some links follow directly from transaction records; others depend on interpretation. Grouping addresses under common control, assigning a service label or connecting activity across an obscured path can involve assumptions. Ask the analyst to identify which method supports each material inference and what could undermine it.
Agreement between tools can provide a cross-check, but ask whether the tools rely on the same underlying source. Repeated labels are not necessarily independent confirmation. The report should describe discrepancies and explain why a particular interpretation was retained.
Avoid converting a confidence label into a legal conclusion. A high-confidence service attribution still needs to be understood in relation to the specific issue the court or recipient must decide.
Read the full explanation: How multi-source investigation tests conflicting findings.
Examine transitions between systems
A route may involve a swap, bridge, exchange or other service. The report should explain the evidence connecting activity on either side of that transition. Similar amounts and nearby timestamps can suggest a lead without establishing a unique connection.
Where a link is unresolved, preserve the gap in the diagram rather than drawing an unqualified continuous line. Ask what additional record or analysis could help resolve it. This is especially useful when deciding whether the next step is more technical analysis or a request for off-chain information.
Privacy tools and incomplete service records can limit attribution. The report should describe the actual limitation instead of promising that every route can be reconstructed.
Ask what the report supports next
End the review by linking the finding to the proposed next action. Is there enough support to identify a service to approach, a data item to seek, or a proposition requiring further expert work? Record the answer separately from any expectation about asset availability or recovery.
A technically useful result may narrow the investigation without identifying a defendant. Clear limits help counsel decide how to use it and prevent an interim finding from becoming an unsupported allegation in later correspondence.
For example, a validated service attribution can identify the recipient of a targeted enquiry. Counsel can then assess the route for obtaining account records, while the report makes clear that the service label alone does not identify its customer. The value is a next step supported by evidence.
Apply the distinction to an example
Optional knowledge check
Two analytics tools show the same service label. What should you ask?
Read the explanation without answering
Whether they rely on independent sources and how the label was validated. Agreement is useful context, but shared source data may explain it.
Review the points you want to take forward
Your review checklist
0 of 4 steps reviewed. This is a learning checklist, not a safety or recovery score.
Answers stay in this tab and reset on reload. The PDF is a concise reference with a blank checklist.
Explore a related guide
Related webinars
References and further reading
Examples are fictional. Checklists are editorial learning aids and do not assess an individual case.

