Based on recurring crypto-user CSV reconciliation complaints · Free & private
Did a wallet transfer turn into a mysterious “sale”?
Put withdrawal and deposit rows side-by-side. This browser-local checker finds plausible same-asset transaction pairs, duplicate rows, competing matches, missing transfers and amount disagreements. It does not decide whether a transfer was yours or taxable.
Outgoing CSV
Enter ONLY outgoing transfers from an account you control, not arbitrary trade rows. UTC time needs a timezone.
Incoming CSV
Enter ONLY incoming transfers. Your source fields stay inside this page.
Compare privately
Kraken Ledger CSV support (beta): For the strictly identified official Kraken txid,refid,time,type,subtype,aclass,asset,amount,fee,balance export, the source's timezone-less timestamp is interpreted as UTC according to Kraken's official ledger field reference. Withdrawals (negative) and deposits (positive) are separated by the type field; trades, staking and internal ledger movements are excluded and counted. Kraken ledger txid is an internal record ID, NOT an onchain transaction hash, so it is only used to recognize duplicates and NEVER trusted as chain proof. Other unknown CSVs still require timestamps with an explicit timezone. No alias between BTC/XBT or other currencies is assumed.
Required columns: timestamp,asset,amount. Optional: txhash,fee. Supported aliases include Date(UTC), Coin, Quantity Transacted and Network Fee. Each timestamp requires Z or ±hh:mm timezone. 1000 rows / 128 KiB maximum per file. No RPC, cookies, wallet, sign-in, tracking, analytics or upload.
Candidate observations — not proof of ownership
No CSVs inspected. Load the invented example to see how the analyzer works.
Financial and tax safety: No blockchain RPC or cost-basis records are accessed. An exact CSV pair or transaction hash does NOT establish your wallet ownership, a non-taxable self-transfer, cost basis, finality, correct transaction history or legal/tax treatment. Different token units, aggregators, bridges, amount fees and missing records can make matches wrong. Do not use this output alone for reporting or payments; consult the original records and qualified professionals.
What would you actually pay to fix?
We are interviewing users about broken exchange imports and USDC invoice/receipt mismatches. Feedback is valuable even if your realistic willingness to pay is $0. Send only an invented or anonymized example, hours lost and whether $0 / $9 / $29 / $99 would be justified to you.
Send optional research feedback ↗
Prefer a developer discussion rather than email? The existing public GitHub user-feedback issue welcomes honest answers (including free-only users), requires a normal GitHub sign-in, and all comments are public. Do not post private data there; the same one-owner team reviews it.
Emailing us may disclose your sender email address. Do not include private wallet details, tax returns, transaction hashes, customer data, KYC documents, login credentials or keys. No payment or feedback is required to use this tool. We have no evidence of paid users of this specific new tool yet. No actual user respondents or paid customers have been independently verified.
Need more than a free preview?
Indicative 15 native Base USDC for a small (up to five) explicitly authorized, redacted source-linked discrepancy memo, subject to separately agreed lawful scope, acceptance, payee verification and payment. No tax return preparation, investment advice, address ownership certification or transaction recovery. Do not prepay an unverified wallet.
Ask about a paid $15 scope ↗ Separate 0.005 USDC paid CSV STRUCTURE API ↗
The VM5 0.005 USDC API only checks generic CSV structure. It does not perform this matching or sell this specific memo. One actual human owns the related VM services.
Original code and tests
Open source matching engine · Original reproducible tests. Disclosed AI-assisted research, not a paid-client reference.