Transaction graph analysis models addresses or entities as nodes and transfers as edges, then tests patterns under explicit time, amount, and attribution assumptions. The worked synthetic dataset shows why one graph can support more than one explanation.
What remains visible
Graph analysis differs across UTXO systems, ERC20 token transfers, TRC20 transfers, bridges, and exchange records. Each network should be interpreted on its own terms.
What it does not prove
A graph pattern is not automatically identity proof. It can suggest relationships, but interpretation depends on evidence quality, tooling, and off-chain context.
Evaluation checklist
- Define nodes and edges plainly.
- Separate patterns from identity.
- Mention timing and amount limits carefully.
- Link to wallet clustering and taint analysis.
Synthetic node-and-edge worked example
The example is deliberately fictional and teaches interpretation limits; it is not a tracing instruction for real funds.
Define the graph
List node identifier, edge direction, amount, asset, network, and timestamp.
Choose the analytical question
Ask about flow, recurrence, timing, or clustering without assuming identity.
Compare explanations
Write at least two models that fit the same edges and name the external evidence needed to choose.
Filled evidence record
Synthetic node-and-edge worked example snapshot: 2026-08-05. The worked record for transaction graph analysis labels every synthetic or non-attributed specimen directly in the table.
| Evidence item | Worked record | Interpretation boundary |
|---|---|---|
| Synthetic edges | 10:00 A→B 100 units; 10:10 B→C 60; 10:11 B→D 40 on one fictional network. | The data shows conservation and timing, not ownership. |
| Explanation one | B may be an intermediary distributing one incoming amount to two destinations. | Purpose and controller are unknown. |
| Explanation two | B may be a treasury or payment account processing unrelated obligations after receiving funds. | The same graph fits a non-mixer explanation. |
Pass or hold criteria
For transaction graph analysis, a missing decisive input remains unknown and blocks the affected conclusion; the synthetic node-and-edge worked example never converts it to a silent pass or zero.
| Dimension | Pass condition | Hold or fail condition |
|---|---|---|
| Dataset | Nodes, edges, time, amount, asset, and network explicit | Narrative with no graph inputs |
| Assumptions | Question and heuristic named | Pattern treated as identity |
| Alternatives | At least two explanations and missing evidence | Single story presented as fact |
Next evidence layer
Blockchain Analytics vs Mixer Claims
Blockchain Analytics vs Mixer Claims adds visibility guide context to transaction graph analysis. Define analytics separately from identity. An analytics label is not always a legal identity, and a mixer claim is not always a verified privacy outcome. Both require context.
How Wallet Clustering Affects Mixer Claims
How Wallet Clustering Affects Mixer Claims adds risk guide context to transaction graph analysis. Define clustering without overstating certainty. A cluster is not the same as a legal identity. It can be probabilistic, incomplete, or dependent on the data available to a specific tool.
Taint Analysis Explained For Mixer Reviews
Taint Analysis Explained For Mixer Reviews adds visibility guide context to transaction graph analysis. Name the model assumption before interpreting a score. A taint score does not automatically prove ownership, intent, legal status, source of funds, or platform outcome. It is an analytical signal that needs method context.
USDT Transaction Visibility Explained
USDT Transaction Visibility Explained adds visibility guide context to transaction graph analysis. Name the visible transaction fields. Explorer visibility does not always identify a real-world person. It also does not prove that an analytics label is complete. It shows the public transaction layer that must be interpreted with additional context.
Source notes
The sources below clarify transaction graph analysis terminology and the evidence limits described above. They do not verify private service operations or guarantee an outcome.
Related questions
What if amount conservation is imperfect?
Fees, partial transfers, other inputs, or incomplete coverage may explain the gap; record the mismatch instead of forcing a path.
What if nodes are labelled by a provider?
Add the label as a dated attribution layer and keep the raw graph available independently.