What do I need to use this?

The transaction schedule you were served, as a CSV, a tab-separated file, or a Concordance-delimited load file — and the chain it is about. No account, no card, and no trace of your own.

Is my document stored?

No. It is read in memory to produce the result and dropped. No row, no column, no party and no amount is written to a database, to file storage, or to a log. That matters if what you were served carries a protective order.

Does this depend on ForensicBlock's data?

No. Every transaction is read from public blockchain nodes — two independent operators where the chain has two, neither of them us. The transaction hash is printed on every row so you can check any of them against a public block explorer yourself.

What does a difference mean?

That the two records disagree, and nothing more. Custodial fees, batched payouts and a gross-versus-net basis all produce genuine differences, and which record-keeper is right is not established by the difference. Both readings are shown so you can decide.

Why does the free check read only some of my rows?

Reading a transaction from the chain costs a request to a public node, and an anonymous tool that spends without limit is a tool that gets switched off. The whole document is READ in full; a bounded sample is checked against the chain, and the rows nobody looked at are counted apart from everything else rather than reported as agreeing or differing.

Free · no account · nothing stored

The other side produced a spreadsheet of crypto transactions.
Has anyone checked it?

A crypto production is the one kind of document in discovery that can be checked against a record the producing party does not control. Every row names a public transaction. Almost nobody reconciles them, because by hand across four hundred rows it is a week of work.

Drop the schedule in below. You will get back what their document actually says, what the chain says, and — stated separately — the rows where the two disagree, the rows they never made checkable, and the rows nothing looked at.

Chain this production is about

CSV, tab-separated, or a Concordance-delimited load file. Your file is read in memory and dropped — no row, no party and no amount is written to a database, to storage, or to a log.

Each transaction is read from two independent public nodes. Two agreeing is the claim; one is not, and every row says which it got.

What this does not claim

A difference is not an accusation. Custodial fees, batched payouts and a gross-versus-net basis all produce genuine differences. Which record-keeper is right is not established by the difference, and this page never says otherwise.
A row nobody could read is not a missing transaction. “We could not read this” and “the chain has no such transaction” are different claims. They are counted apart, and so are the rows a bounded free check never looked at.
The binding rate is not a failure rate. A row counts as corroborated only when every comparable field agrees, so one recurring difference collapses the headline while destination and timing may agree on every row. The per-field decomposition is always shown beside the rate.
Nothing here is a sealed exhibit. This is a check. A production you can put in front of a court carries Bates numbers, a custody record, a named examiner and a verifier the recipient can open — that is the engagement, not this page.

Investigation answers 'what happened.' Forensics answers 'can you prove it to a court.' We produce the exhibit.

If the schedule you just checked is going into a motion, the next step is the whole document read, reconciled and produced as an exhibit — Bates-labelled, custody-recorded, signed by a named examiner, and verifiable by the recipient without an account.

Scope a matter Verify a sealed exhibit

Questions

What do I need to use this?: The transaction schedule you were served, as a CSV, a tab-separated file, or a Concordance-delimited load file — and the chain it is about. No account, no card, and no trace of your own.
Is my document stored?: No. It is read in memory to produce the result and dropped. No row, no column, no party and no amount is written to a database, to file storage, or to a log. That matters if what you were served carries a protective order.
Does this depend on ForensicBlock's data?: No. Every transaction is read from public blockchain nodes — two independent operators where the chain has two, neither of them us. The transaction hash is printed on every row so you can check any of them against a public block explorer yourself.
What does a difference mean?: That the two records disagree, and nothing more. Custodial fees, batched payouts and a gross-versus-net basis all produce genuine differences, and which record-keeper is right is not established by the difference. Both readings are shown so you can decide.
Why does the free check read only some of my rows?: Reading a transaction from the chain costs a request to a public node, and an anonymous tool that spends without limit is a tool that gets switched off. The whole document is READ in full; a bounded sample is checked against the chain, and the rows nobody looked at are counted apart from everything else rather than reported as agreeing or differing.