Loading ForensicBlock
Preparing your blockchain forensics platform...
Preparing your blockchain forensics platform...
The third pillar made operational. Type an address (or hash, or matter name) anywhere in the platform → debounced dropdown surfaces every matter, investigation, watchlist entry, screening record, exhibit, and digital asset that touched it. Conflict check runs on intake so prior touches surface BEFORE engagement.
ConflictCheckWidget runs a debounced fb_conflict_check as the user types the seed address. Surfaces prior matters / investigations / watchlist / assets within privilege scope.
GlobalSearch sits left of the org picker. Reads the active org from cookie. Searches matters / investigations / watchlist entries / screening records / exhibits / digital assets.
Every query is gated through fb_user_is_org_member. Never returns cross-org data. Per-matter ACLs respected when the layer wires in.
Type the seed address into the intake form.
Debounced 600ms. Calls fb_conflict_check; shows prior matters/investigations/watchlist hits.
Informational — non-blocking. The partner sees the conflicts and either proceeds, requests waivers, or declines.
Header search box. Type 3+ chars; debounced 250ms. Dropdown groups results by entity type.
Every matter persists indefinitely. Methodology version pinned per matter so historical work stays reproducible.
Honesty rail
Cross-matter visibility respects org boundaries — we never return one firm's data to another firm. Per-matter ACLs (when granted) further scope visibility within the org.
Book a demo and bring a closed matter (or a hypothetical one).