People export transaction history for one main reason: tax reporting. Specifically, cost basis tracking — you need to know what you paid for tokens and when, in a format a tax tool or accountant can actually read. Portfolio analysis and fee reconciliation are real secondary uses, but they're less urgent for most people.
The complication is that there isn't one method. How you export depends on whether you're pulling from a centralised exchange or a self-custody wallet, which chain you're on, and what level of detail the export actually contains. Neither source hands you a complete picture automatically. For anyone who's moved funds between exchanges and self-custody wallets, you'll need to combine multiple exports.
From Centralised Exchanges
Most major exchanges — Coinbase, Binance, Kraken, Gemini — have a built-in export function, usually under Account History or a dedicated Tax Centre section. The output is typically a CSV.
What that CSV contains varies significantly by exchange:
- Coinbase includes date, transaction type, asset, quantity, spot price at the time, and fee. The fee column matters — it affects cost basis.
- Binance generates separate reports for spot, futures, and margin activity. These don't auto-combine, so you need to be deliberate about what you're exporting. If you've used more than one product, you'll need multiple exports.
- Kraken has a time range cap per export. For multi-year history, you'll need to run several exports and stitch them together.
The practical flow: go to the tax or history section, set your date range (all time if possible, or by tax year), choose CSV, download, then spot-check the transaction count against what you expect to see.
One thing people consistently miss: exchange exports only capture what happened on that exchange. If you withdrew tokens to a self-custody wallet and did anything else with them — swapped on a DEX, staked, added liquidity — that activity isn't in the exchange export. It needs to be captured separately.
From On-Chain Wallets (Self-Custody)
For wallets like MetaMask, Phantom, or a hardware wallet connected to Ledger Live, the wallet application itself doesn't provide a complete transaction export. The transaction list the app shows you is a display of on-chain data — the actual history lives on the blockchain, not inside the app.
The correct method for self-custody wallet history requires your public wallet address. Not your private key, not your seed phrase — those are never needed for this, and if something is asking for them, stop.
For Ethereum and EVM-compatible chains:
- Copy your public wallet address
- Go to Etherscan.io and paste the address into the search bar
- On your address page, scroll to the transactions tab and find the download icon — it exports up to 5,000 transactions as a CSV
- Repeat for the Token Transfers tab (ERC-20 activity) and the NFT Transfers tab — these are separate exports from regular ETH transactions
For Solana, the equivalent explorer is Solscan. For BNB Chain, it's BscScan. Each chain has its own explorer and its own export.
That's the part that surprises people: multi-chain activity means multiple exports. Ethereum mainnet, Arbitrum, Optimism, Base, and Solana are all separate chains with separate histories. There's no single export everything function.
Through Crypto Tax Software
The cleaner workflow for anyone with meaningful on-chain activity is to let tax software handle the import side. Tools like Koinly, Cointracker, and Taxbit connect via API for exchanges (you grant read-only API access) and via public wallet address for on-chain activity. They pull the history, classify events, and allow you to export the processed data in standard formats.
This doesn't eliminate the underlying problem. It just moves it one layer. The software still needs all your wallet addresses and exchange connections to be complete — and it still inherits the gaps. DeFi interactions often come through as unclassified contract calls that the software misidentifies or fails to label correctly. NFT and yield farming activity in particular tends to require manual review.
That said, for anyone with more than 100 transactions, doing this manually in a spreadsheet is unreasonable. Tax software is the practical path.
Where Constraints Live
The binding constraint is completeness. Every source has limits:
- Etherscan exports cap at 5,000 transactions per tab. If you've been active on a single address for years, you'll hit this. Workaround: use date-range filtering to break the export into annual chunks.
- Exchange exports frequently have time range limits and don't backfill historical rate data for unusual assets.
- DeFi interactions appear as raw contract calls in on-chain exports — the classification (swap, liquidity provision, yield claim) requires interpretation by tax software or manual labeling.
There's no clean solution to multi-chain fragmentation right now. Cross-chain indexing exists, but producing a unified export from those tools requires either using a third-party tax product or working with APIs, which isn't practical for most users.
What's Changing
The 1099-DA broker reporting rule (US) changes the verification requirement starting with 2025 tax year returns. Exchanges must now file 1099-DA forms directly with the IRS. That means your self-generated transaction export needs to reconcile with what the exchange reported — not just be internally consistent. Discrepancies between your export and the 1099-DA you receive could create issues. Checking your export against any 1099-DA form becomes a meaningful step in the filing process.
For on-chain activity, no equivalent reporting requirement exists. DeFi protocols don't file 1099s. The export process there remains entirely manual and self-reported.
What Would Confirm This
1099-DA implementation proceeds on schedule for 2025 tax year. Exchange export formats improve to align with reported data. Tax software classification improves for DeFi events, reducing the volume of manual corrections.
What Would Invalidate It
Congressional action delays or narrows the 1099-DA scope — in that case, the reconciliation step against broker-reported data matters less. A unified cross-chain export layer that consolidates multi-network activity into a single file would simplify the process significantly, but doesn't exist in practical form yet.
Timing
Now: Pull exports for all sources — exchanges and self-custody wallets — before filing. Verify transaction counts. If you hit Etherscan's 5,000-transaction limit, use date-range chunking.
Next: For 2025 tax year returns, expect 1099-DA forms from exchanges. Cross-reference your exports against those forms.
Later: Multi-chain export tooling is improving but fragmented. Don't rely on a single-source solution for current-year filing.
This covers the mechanical process of exporting transaction data for record-keeping and tax preparation. It doesn't constitute tax advice, doesn't address which cost basis method to use, and doesn't recommend any specific software. The export is an input to the tax calculation process, not the calculation itself.
