One DeFi transaction. Several CSV rows. Which need review?
When swaps, liquidity pools, staking or bridges turn into ledger rows, the same onchain transaction may generate several transfer events. Before declaring a gain or income, identify what is still ambiguous.
Use this free, local-only transaction CSV exception inbox. No wallet connection, no blockchain API, no keys, no account and no uploaded CSV. Review prompts—not tax classifications.
Accepts EVM/explorer-like CSV exports up to 256 KiB, 750 data rows and 35 columns, with common transaction hash / method / amount / address header aliases. Not all wallet exports include the necessary fields. This first release does not decode smart-contract logs, price assets or infer wallet ownership.
Inspect your DeFi export in this browser
Use a non-confidential CSV you are allowed to inspect. You can load a fictional file first to see how it works. Raw addresses, amounts and notes are not printed into the results. Only fixed review prompts and CSV row numbers appear.
Download includes row numbers, suggested review prompts and, only if checked, validated EVM transaction hashes. Your original source CSV is not uploaded, sent to a merchant or logged by this page.
What this catches
- Possible swaps and LP activity: hints from a declared method/action string, not a decoded token swap.
- Possible rewards, lending and bridges: flag ambiguity for human inspection.
- Multiple events sharing one transaction hash: note potential double-counting instead of silently removing rows.
- Missing or malformed source fields: hash, date, amount, header mismatch.
- Same sending/receiving address: a review clue, not proof of a self-transfer or no tax liability.
What this does not do
- No live wallet syncing, blockchain verification or DeFi protocol ABI decoding.
- No token prices, realized gains, cost basis, yields, tax law or loss calculations.
- No automated labeling of swaps as disposals or bridging as nontaxable.
- No wallet connect, transaction signing, swaps, investment recommendations or token approval requests.
- No guarantee that a source CSV is complete or correct.
Did an importer mistake two equal-size trades for one?
An exchange trade ID, fill ID or order ID is not interchangeable with the amount. Do not auto-delete legitimate rows just because two asset quantities match. Our free browser-local trade-ID duplicate audit flags repeated/missing IDs, exact rows and same quantities with different IDs, and outputs only row numbers, not transaction details. No data upload, wallet, tax calculations or payment. One order ID can span several genuine fills; findings need manual source review.
Check trade IDs locally for free ↗Missing the other half of a wallet transfer?
Kraken withdrawals versus wallet receipts
One EVM explorer CSV cannot establish whether a row was an exchange withdrawal, a different wallet's deposit, a bridge hop or a taxable sale. If you have a withdrawal export and a wallet receipt export, review candidate pairs before importing them into a tax tracker.
Our same-owner VM3 two-CSV tool checks time windows, asset/amount, optional fee and duplicate candidates. It recognizes a documented Kraken Ledger CSV shape: its txid is an internal Kraken ledger ID, NOT an independently finalized blockchain transaction hash. Trade, earn and internal movements require separate review.
This link opens the original separate VM3 GitHub Pages site, owned by the same single beneficial human. Following the link sends NO CSV, wallet address or tax record from this page; use the other local-only checker with non-confidential files. Neither checker connects a wallet or computes tax/cost basis or certifies ownership/onchain settlement. Kraken's official Ledger field definitions.
Have a business invoice and a reported Base USDC payment?
Use the right matcher—not a DeFi tax-event checker
If you need to reconcile a business invoice to a self-reported Base USDC transfer CSV, the DeFi method-label checker above is the wrong tool. Try the original VM5 free invoice-to-USDC CSV candidate matcher.
It compares an invoice export with a receipt-event export, groups chain:tx_hash:log_index duplicates conservatively and highlights unmatched, partial and ambiguous receipts. Both files are processed locally in the buyer's browser, with no signing, RPC verification or payment for the free preview.
15 native Base USDC — 50-row exception review pilot
Deliverables after actual acceptance
For up to 50 flagged, owner-authorized, non-sensitive EVM CSV records, we can prepare a traceable review checklist with transaction grouping suggestions, data gaps, ambiguous method explanations and original public-explorer links where available. One brief revision within the written scope. A specific delivery deadline must be agreed before any payment.
No audit, financial certification, professional tax opinion, asset recovery guarantee, wallet management or promise to repair hidden transaction history.
Before any USDC is sent
Contact us with the network, approximate record count, anonymized header names, the largest discrepancy and whether you want a written quote. We will check whether the task is possible, agree a price and lawful file-sharing/payment/cancellation arrangement, and identify the receiving Base native Circle USDC address in the written contract. Do not send coins or original private financial exports without confirmed agreement.
Ask about one paid review ↗Evidence: the tool code and test cases are public for inspection. Its heuristics cannot assign a legal tax category. A paid manual review is merely a proposed service—not a merchant x402 subscription, approved contract, new customer or received payment.
Your real feedback matters more than page views
Which problem would you actually pay someone to resolve: missing source transactions, repeated event legs, LP/reward ambiguity, failed CSV import or something else? Tell us what explorer/app you tried and what the tool got wrong. Do not include addresses, full transaction hashes, personal identities, private keys or private balances. Use the optional consent-based feedback form below without providing a contact email. GitHub issues are public and require sign-in; email is a separate private option.
One-minute feedback (optional; no email required)
Only provide a problem category, export software, and optional brief general feedback. Do not include your CSV, wallet addresses, full transaction hashes, balances, legal/tax identifiers, phone, seed phrases or private keys. This is feedback, not an order or a payment.
Independent user reviews received at launch: 0 confirmed. Paid customers: 0. We will treat future comments as evidence only when they come from actual external users, not our own VM accounts.
Research context: public user experiences on missing CSV/export rows and manual DeFi reconciliation. These are independent discussions, not testimonials or endorsements of this tool.