How to export my full transaction history from MetaMask for taxes?

Accessing Transaction Data via MetaMask Interface

1. Open MetaMask browser extension or mobile application and ensure you are logged into the correct wallet address.

2. Navigate to the Account tab and select Activity to view all on-chain transactions associated with that address.

3. Scroll down to load historical entries; note that MetaMask does not natively support bulk export of full transaction history within its UI.

4. Click on individual transactions to inspect details such as timestamp, block number, gas used, and token transfers—these fields are essential for tax classification.

5. Use the “Copy” button beside transaction hash to manually record entries for spreadsheet collation when preparing documentation.

Exporting via Blockchain Explorers

1. Copy your wallet address from MetaMask and paste it into Etherscan (for Ethereum), BscScan (for BNB Chain), or corresponding explorers matching your network.

2. On the explorer page, locate the Transactions tab and verify the list matches your MetaMask activity log.

3. Click Export CSV at the bottom of the transaction table—this generates a downloadable file containing hash, date, value, fees, and status.

4. Repeat this process for each connected network if your wallet holds assets across multiple chains like Polygon, Arbitrum, or Base.

5. Import each CSV into spreadsheet software and consolidate rows using uniform date formatting and currency denomination columns.

Using Third-Party Tax Aggregation Tools

1. Connect your MetaMask wallet directly to platforms such as Koinly, CoinTracker, or TokenTax through their wallet import feature.

2. Authorize read-only access—no private keys or seed phrases are shared during this step.

3. Allow the tool to sync historical data by scanning blockchain nodes; syncing time varies depending on transaction volume and chain congestion.

4. Review auto-categorized entries: deposits, withdrawals, swaps, NFT trades, staking rewards, and airdrops are tagged with applicable tax event types.

5. Generate jurisdiction-specific reports including capital gains worksheets, income summaries, and cost-basis calculations compliant with local tax authority requirements.

Handling Multi-Chain and Cross-Protocol Activity

1. Identify all protocols interacted with—Uniswap, Curve, Aave, Blur, Magic Eden—and confirm whether their events appear in standard explorer exports.

2. For complex DeFi interactions involving flash loans, liquidity pool exits, or yield compounding, rely on specialized parsers embedded in tax tools rather than raw blockchain data alone.

3. Manually add off-chain events such as fiat deposits via exchanges or peer-to-peer transfers where no on-chain trace exists but regulatory reporting mandates inclusion.

4. Reconcile discrepancies between MetaMask’s displayed balance and aggregated portfolio values by checking token contract addresses and decimal precision alignment.

5. Preserve screenshots of protocol interface confirmations and wallet approval signatures as supplementary audit evidence when substantiating trade origins.

Frequently Asked Questions

Q: Does MetaMask store private keys on its servers?A: No. MetaMask is a non-custodial wallet. Private keys remain solely in the user’s browser storage or device, never transmitted to external servers.

Q: Can I export ERC-20 token transfers separately from ETH transactions?A: Yes. Etherscan allows filtering by token contract address. Exporting requires selecting “Token Transfers” instead of “Normal Transactions” before clicking “Export CSV”.

Q: Are internal smart contract calls included in exported transaction lists?A: Standard CSV exports from explorers include top-level transaction hashes only. Internal operations require API-based extraction or advanced tools supporting trace-level parsing.

Q: What happens if I change my MetaMask password or reinstall the extension?A: Your wallet remains accessible as long as you retain the original 12-word recovery phrase. No transaction history is lost because it resides immutably on-chain, not in the extension itself.