Loading ForensicBlock
Preparing your blockchain forensics platform...
Preparing your blockchain forensics platform...
Chainalysis auto-generates a narrative the analyst trusts. ForensicBlock lets the EXAMINER write it. Section by section, with every sentence anchored to a finding, transaction, address, or audit-log entry. When the examiner seals the story, the SHA-256 of the canonical content anchors — and the SQL trigger refuses any post-seal mutation. The seal is final.
10 canonical section kinds (executive_summary, background, methodology, findings, fund_flow, risk_assessment, limitations, conclusions, recommendations, custom). Add, edit, reorder.
6 citation kinds (finding, transaction, address, edge, audit_event, external). Anchor each claim. Opposing counsel reads every line.
Status → sealed stamps content_sha256 + sealed_at + sealed_by. The SQL trigger refuses any further mutation of the sealed core.
Story Builder sits below the auto-narrative on every detail page.
Examiner writes section by section. Drag-reorder. Add custom sections. Long-form serif rendering for legibility.
Add citations per section. Each citation kind has the right input (finding ID, tx hash, address, etc.).
Save without sealing. Iterate until ready. Multiple drafts allowed; only one sealed per investigation.
Status flips to sealed. SHA-256 anchors. Re-opening creates a NEW draft; the seal trail is preserved.
Honesty rail
Honesty rail visible on every draft: 'YOU write the narrative. The platform never auto-fills sentences. Every citation is yours; opposing counsel will check each one. Under-claiming reads better than over-claiming.'
Book a demo and bring a closed matter (or a hypothetical one).