VISUAL CRYPTO INVESTIGATIONS

Follow the records.
Inspect the evidence.

START A WORKBOOK

Import a UTF-8 transaction CSV or open the fictional sample. Up to 500 transfers, 1 MB.

CSV format & evidence handling

Required columns, in any order. One transfer per transaction event index. Network identifiers must be lowercase. Amounts are atomic integer strings; decimals range from 0 to 36. UTC timestamps use YYYY-MM-DDTHH:mm:ssZ. Use a contract identifier for tokens, or native for a network’s native asset. No chain-specific address validation is performed.

chain,tx_hash,event_index,from_address,to_address,asset,asset_id,amount_raw,decimals,timestamp,source,retrieved_at

Source must identify the supplying file, provider or collection method. Retrieval time is supplied by you. Raw UTF-8 input is preserved within the export. Import replaces the current session. Save an encrypted case to resume later, or export unencrypted evidence JSON for independent review. No automatic save.

0 / 0Visible transfers

0Network-scoped addresses

0Pinned source records

TRANSFER VOLUME · NOT NET LOSS OR RECOVERABLE FUNDS

No transfer volume to display.

0 filters active

Your evidence starts here

Open the sample to explore, or import your own structured transfer records.

CROSS-SOURCE INVESTIGATION

Profiles. Payments. Platforms.

Keep the source record attached to every connection, then test competing flow explanations.

Connect evidence, not assumptions.

Import a JSON dossier of creator profiles, hosting platforms, checkouts, payment accounts and wallet references. Each relationship requires a source, rationale and alternative explanation.

Creator profileHosted contentCheckout linkPayment accountWallet reference

Public captures and lawfully supplied records only. No private-content access, account bypass or automatic person identification. The sample button becomes available with the fictional transfer dataset.

What to include in a platform dossier

The example schema contains sources (preserved text, collection time, locator, stated access basis and source family), scoped entities, and relationships with observed/asserted/hypothesized status. References must resolve. Same-controller links are accepted only as hypotheses. This release supports unreviewed and disputed states; it cannot authenticate a reviewer.

Preserve conflicts as separate disputed relationships. URLs are retained as inert source text; this workbench does not fetch them or recover deleted/private content. Evidence is included in the main export.

INDEPENDENT VERIFICATION

A trail another analyst can check.

Exports include the original CSV, normalized transfers, filters, visible record IDs, exact totals, pinned records, your hypothesis, platform evidence and the current flow model in a SHA-256 envelope. Every export contains the full source, including filtered-out records.

Download offline verifier python3 verify_bundle.py Waybrio_evidence.json --digest YOUR_RETAINED_SHA256Save the digest separately. A matching hash proves consistency with that digest, not the truth of a source.

Validation boundary & remaining production work

Imported records are user-supplied assertions, not independently corroborated blockchain observations.
A transfer or graph connection does not establish identity, common ownership, criminal intent or control of subsequent funds.
Coverage, confirmations, finality, reorgs, bridge continuity and external labels are not verified by this version.
SHA-256 detects changes relative to a trusted digest; it does not establish source authenticity or legal chain of custody.
Work is held in browser memory until saved to a case file. No shared case store, authenticated reviewer sign-off or tamper-evident audit service is implemented.

Before operational police use: independently validate supported chains and parsers, implement agency access controls and audit retention, test restore and evidence handoff, and complete an investigator-led pilot. No police endorsement or admissibility claim is made.