What we shipped, what we are building, and what comes next.
Forensia is built in the open. Every feature is listed here with its real status, so you can tell what you can use today from what is still on the bench. Nothing on this page is a promise of a date.
In progress
Being built now. Not usable yet.
Reading storage inside nested calls
Working out which contract's storage each step of a transaction read or wrote, including inside calls made by other calls. Developer-side groundwork for now, run in isolated containers; nothing in the workspace shows it yet.
What a step depended on
For a supported step, recording the earlier reads and writes it relied on, so a later rule can point at its evidence. Also groundwork: not visible in a result yet.
One re-entry candidate rule
A single, inspectable rule that flags a possible stale-state re-entry and shows the steps it rests on. The rule and a review panel now exist and run against synthetic test cases in the developer console. It is not connected to real lookups yet, and it will raise a candidate to check, never a verdict of theft.
Built, in review
Finished and tested, waiting for release. It can still change.
Bounded Ethereum token balances
Built and tested locally: discover a limited set of Ethereum ERC-20 candidates and check selected balances at a named block. Not enabled on the hosted site. No complete portfolio, fiat valuation, NFT inventory or all-network token coverage is claimed.
Planned
Intended, with no date. Plans change.
Replay one historical transaction exactly
Re-run a past transaction against the state it actually ran on and compare the outcome with the recorded receipt. Two feasibility checks, on October 7 and 8, could not obtain the full starting state for the test transaction, so whether it can be obtained is still not established and no work on the replay itself has started.
A labelled what-if beside the replay
Change one stated input and re-run, with the hypothetical result shown separately from what was observed. Depends on the replay above.
Opt-in explanations grounded in the evidence
A plain-language explanation of a selected finding that cites the exact records and quantities it uses and keeps unknowns as unknowns. Off unless you ask for it.
Suggested next steps
Bounded, budgeted suggestions for what to check next. They propose; they do not run anything or change a review on their own.
Live
Released. You can use it today.
Large transactions, without losing the record
Accepted Bitcoin transactions retain all inputs and outputs within the source and 2,048-record bounds, with exact fee reconciliation when previous-output values are available. EVM transactions retain up to 2,048 token-event items, including up to 256 per batch, plus bounded call traces. Activity, receipt and step pages stay small; saves and reports keep the retained record. Missing data and graph samples remain explicit.
Read moreClearer control over optional analytics
The first-search form now shows an unchecked, optional analytics choice, separate from required signup. Change it later in the footer; both controls stay in sync. Turning measurement off keeps the option to request deletion of earlier usage. Exact searches and contact-linked usage remain disabled on the hosted site.
Read moreMore reliable optional usage measurement
Section timing avoids counting two active tabs at once. Quick signups are counted in the right order, only while analytics consent is active. Export preparation and download clicks are separate; a click does not prove file delivery. Exact searches and name-linked usage remain off on the hosted site.
Read moreClearer wallet, contract and transaction results
Shorter explanations, readable transaction receipts, separate fees and movements, and clearer account and permission context. Overview, Activity, Connections, Analysis and Sources stay directly accessible. Missing checks remain unknown, not zero or safe.
Read moreActivity charts, filters and exact record positions
See when captured activity happened, filter by direction, asset or execution status, and group records by transaction. Supported events keep their exact occurrence positions. Counts distinguish retained records from omitted history; a chart is not a lifetime activity record.
A clearer graph for following connections
The investigation panel has its own space, node details scroll within the canvas, and dense graphs show fewer overlapping labels. Pan, zoom, inspect records and follow captured paths; expanding a node is a separate bounded lookup, not proof of shared ownership.
More precise Bitcoin, look-alike and bridge findings
Tighter Bitcoin ordering, locktime and replacement-signalling checks; look-alike comparisons link to their captured occurrences; bridge event checks reject mismatched emitters and layouts. Similarity is not attribution, and a source deposit alone is not destination settlement.
Compact coverage and source inspection
Coverage limits appear together with short explanations and their original captured wording. Long source lists scroll inside their panel. Saved results and permitted reports preserve capture times, source links and the distinction between partial, failed and unchecked fields.
Optional product-usage measurement
Separate, default-off consent for visits, search types and networks, section engagement and reliability. Hosted analytics does not collect exact searched addresses or link usage to your name. Private reports are not public. The mandatory signup form is unchanged.
Read moreCall paths and account context
Each recorded call keeps its place in the call tree, with who called, whose code ran and whose storage was in play, including delegated and read-only calls. Missing or unsupported context stays marked unknown.
Permissions linked to the exact call
An approval or revocation is compared with later transfers by the same spender and linked to the recorded call that matches, so you can open the step itself.
Transaction execution context
Fees are kept apart from transfers, and each transaction is read under the Ethereum rules in force at its block. Where the context could not be captured, the result says so.
Failed steps explained
A transaction can succeed while a step inside it fails. Those steps are called out, and an error in one call is kept apart from a rollback of the call around it.
Timelines ordered by position in the block
Saved timelines are ordered by where each transaction sits in its block, and a recorded time that disagrees with the block header is shown as a disagreement, not smoothed over.
Review notes tied to evidence
Notes and corrections on a saved investigation can point at several exact records, with a role for each piece in the episode. Links are listed beside the timeline.
Attach a document to a saved investigation
Keep a report or post beside a saved investigation as a text file: the original text, the exact excerpts you select, and the addresses and transactions it mentions. Everything stays in your browser and is marked as outside material, not a chain record. Mentions are not looked up or turned into findings.
Follow a trail one step at a time
Optional, budgeted follow-up checks for native value, tokens and Bitcoin spends. Each step is saved, can be cancelled, and can be recovered from a backup.
One bridge journey, matched end to end
For a supported Across transfer, the deposit on one network is matched to its fill on another from the recorded events. One bridge only; a journey that cannot be matched is left unmatched. It does not yet confirm which version of the bridge's code handled the transfer. A test on October 8 showed the execution traces for that can be obtained for two sample transfers, but the check itself is not built, so that part stays marked unverified.
Bitcoin allocation comparisons
When a transaction mixes several inputs, different ways of assigning outputs to inputs are shown side by side with the assumption each one makes. None is presented as the answer.
Compare two captures
Two captures of the same address can be read against each other, with the window each one covers stated, so a difference in coverage is not mistaken for a change on chain.
Case studies, docs and blog
Six case films with step-by-step replays, 56 docs pages on how each part of a result is worked out, and a blog with 25 posts explaining how each feature works and where it stops. This page is part of the same release.
A redesigned workspace and site
A new look for the workspace and the site, a light theme, ambient sound you can mute, and a guide that tours the whole site or just the view you are on.
Analysis that fits what you searched
The Analysis view now opens with a short fact sheet and changes with the subject: a contract leads with its code and who stands behind it, a wallet with who it dealt with, a transaction with what its records show. Each finding is one line until you open it.
Phishing-list matches stay on screen
A match against the third-party phishing list is shown in the result but is left out of saved results, backups and reports. Run the lookup again to see it; a saved copy with no match says nothing either way.
Tighter limits against abuse
A security review before release closed several ways to waste the free service: lookups with no verification are refused sooner, a signup name can hold letters only, and an address gets at most one confirmation email a week.
Newsletter and signup confirmation
A confirmation email on signup, and a newsletter that lists new releases, case studies and blog posts, with one-click unsubscribe. A signup is kept until you withdraw it, for two years at most; people who joined earlier for product updates get product updates only.
Save and reopen an investigation
Keep up to two captured results in an investigation, add notes and corrections, export a JSON backup or a Markdown report, and remove them when you are done. Stored in your browser only.
One-input lookup
Paste an address, a contract or a transaction. No wallet connection and no signature.
Eight networks
Bitcoin, Ethereum, Base, Arbitrum One, Optimism, Polygon PoS, BNB Smart Chain and Avalanche C-Chain. Each lookup reads a bounded slice of history, not everything.
Read moreEVM transaction inspection
Native value, token and NFT transfers, the outcome the receipt records, and optional bounded call traces.
Contract context
Verified metadata where it exists, proxy routing, administrative changes seen in the records, and how the contract was created.
Bitcoin inspection
Inputs and outputs, spend links, fees, bounded tracing, and leads on change outputs and privacy patterns. A lead is a reason to look, not a conclusion.
Analysis linked to evidence
Pattern checks, look-alike address comparisons and transfer timelines, each opening the exact records it rests on.
Public screening context
Dated exact-address checks against the OFAC list and ScamSniffer reports, and selected protocol labels. No match is not a clearance.
Overview, Activity, Connections, Analysis and Sources
Five views of one result, with filters and links between a finding and the record behind it.
Source records and reports
Capture times, source references and fingerprints for every response, and a Markdown report you can download.
Pro features
Paid features will be listed here, with the same status labels as everything else.
No Pro features are announced yet. Everything listed above is part of the free beta.