2. Inspect the activity
Arrows show recorded sender → recipient. Click a node to filter transfers. Gold is the subject address, green is a direct counterparty, and purple is an indirect counterparty. Relationships do not establish identical funds or common ownership.
Case scope & findings
AML activity review
Descriptive indicators help prioritize review. They do not score risk or establish suspicious activity. Review the evidence, record an explanation, and make your own assessment.
Use only an expectation you can support. This is not a regulatory threshold.
Subject counterparty ledger
Ranked by total incoming plus outgoing USDT within the returned scope. Totals are not balances. Select a counterparty to inspect its evidence.
| Counterparty | Incoming USDT | Outgoing USDT | Events |
|---|
Candidate sequences
Equal positive amounts recorded sequentially through an intermediary within 30 minutes, up to 20 pairs. These are leads, not proven funds flows. Click to filter that intermediary.
Transfer evidence
| UTC / block | Sender | Recipient | USDT | Transaction / log |
|---|
3. Record your assessment
Notes stay in this tab and are not sent to the node or saved to a server. Use Save portable case file before closing or refreshing, then Open case file to resume later. Switching cases preserves notes only while this tab remains open.
Pinned transaction evidence
Open a transaction above and pin it to your case. Pins travel with your exported report.
Review checklist
4. Quality control review
Submit a copy of the evidence and assessment for QC. A reviewer can record findings, return the case for correction, or document a completed review. Save the portable case file to share the full history.
This is a file-based workflow prototype. Names are self-reported; reviewer identity, separation of duties and a tamperproof audit trail are not enforced. QC completion is not a determination that activity is lawful.
Review the submitted snapshot
Review history is included in the portable case file and case summary. Later edits require a new submission. Use the snapshot below each submission to inspect exactly what was reviewed.
Provenance & limits
New queries retain raw node requests and responses in the evidence export. The saved example’s raw evidence is in GitHub under data/raw. Block hashes are checked against node responses; saved-case checksums are verified at build time. Neither check is cryptographic proof of inclusion. Provider completeness is assumed. An event sender is not necessarily the transaction signer. Opening balances, KYC and exchange fiat-conversion records are not available here.