How to Export Your Metamask Transaction History: Complete Guide 2025

Metamask is the most widely used cryptocurrency wallet in the world, with more than 30 million active users interacting daily with Ethereum, Polygon, BSC, Arbitrum and dozens of blockchain networks.

But when the time comes to prepare your income tax return or respond to a request from the AEAT, many users discover a fundamental problem: Metamask does not have a native history export function like centralized exchanges.

Exporting your Metamask data incorrectly or incompletely can result in:

• Incorrect tax returns that lead to penalties
• Inability to justify the origin of your cryptocurrencies to the Tax Agency
• Loss of traceability over complex DeFi operations
• Incorrect calculations of the mandatory FIFO method in Spain
• Omission of swaps, airdrops or yields that must be declared

In this complete and updated guide for 2025, we explain step by step how to correctly export all your Metamask operations, which tools to use, how to interpret the data and how to organize them for your tax return before the AEAT.

Unlike exchanges such as Binance or Coinbase, Metamask is a non-custodial wallet. This means that your private keys are under your exclusive control, but it also means there is no centralized server that stores and provides you with a transaction history in CSV format.

All your transactions are recorded on the blockchain, which is an advantage for traceability, but it means you must use block explorers or specialized tools to extract and process that information.

Key differences between Metamask and centralized exchanges

Tax obligations with wallets like Metamask

As a Metamask user in Spain, your tax obligations are exactly the same as with any other form of cryptocurrency holding. Every time you sell, exchange or convert cryptocurrencies via a swap on a DEX, you generate a capital gain or loss that must be declared in Form 100 applying the FIFO method.

If the total balance of your cryptocurrencies in non-custodial wallets such as Metamask exceeds €50,000 on 31 December, you are required to file the Form 721 for cryptocurrency declaration. Non-custodial wallets are considered "abroad" for the purposes of this form.

In addition, yields generated by staking, yield farming, airdrops and other DeFi operations must be declared as investment income, as we explain in our DeFi taxation guide.

Metamask records multiple types of operations, each with different tax implications. For a complete tax return, you need to identify and export all relevant transaction types.

1. Incoming transfers (Receive)

These include cryptocurrency deposits from exchanges, transfers from other wallets, airdrops received and reward tokens from staking or farming.

Tax implications:

• Deposits from your own exchanges or wallets do not generate taxation (they are internal movements)
• Airdrops received must be valued at the market price at the time of receipt
• Rewards from staking or farming are investment income

2. Outgoing transfers (Send)

These include sending cryptocurrencies to exchanges, transfers to other wallets and payments for goods or services.

Tax implications:

• Transfers to your own exchanges or wallets are not taxable if you can prove you control both addresses
• Payments for goods or services do generate capital gains/losses
• Each transfer includes gas fees that may be deductible

3. Swaps on DEXs (Uniswap, SushiSwap, 1inch, etc.)

Token swaps performed directly from Metamask or by connecting the wallet to DeFi protocols are operations with high tax relevance.

Tax implications:

• Each swap is a taxable exchange that generates a capital gain or loss
• Even swaps between two cryptocurrencies (ETH → USDC) are taxable
• Gas fees paid in these operations are deductible expenses
• It is essential to understand the correct tax treatment of each type of operation

4. Contract approvals (Approvals)

When you connect Metamask to a DeFi protocol, you usually have to approve that the smart contract can spend your tokens.

Tax implications:

• Approvals themselves do not generate taxation
• However, they consume gas, which is indeed an expense
• It is important to record them for full traceability

5. Complex DeFi operations

These include providing liquidity in pools (Uniswap, Curve), deposits in lending protocols (Aave, Compound), token staking, reward claims and bridging operations between networks.

Tax implications:

• Each type of operation has a specific tax treatment
• Rewards must be declared as income when received
• Impermanent loss in liquidity pools can be offset against gains

6. Failed transactions

Transactions that fail due to lack of gas or contract errors are also recorded on the blockchain.

Tax implications:

• They do not generate capital gains or losses (there was no exchange)
• The gas consumed is a real expense that can be documented

There are several ways to obtain your Metamask operations history, from manual methods to automated tools. Let’s look at each option.

Method 1: Blockchain explorers (Etherscan and similar)

The most direct way to obtain your history is by consulting the official blockchain explorers of each network where you have operated.

For Ethereum (mainnet):

1. Go to etherscan.io
2. Paste your Metamask wallet address into the search bar
3. You will see all your transactions on the Ethereum network
4. Click on "Download CSV Export" (bottom right corner of the table)
5. Select the date range
6. Download the CSV file

Explorers by network:

This method has some important limitations: you must export manually from each network where you have operated, the CSVs only include basic transactions without the internal DEX swaps, they do not show the EUR price at the time of the operation, internal contract operations may not appear, and it requires manually consolidating multiple files.

However, it has significant advantages: you obtain data directly from the blockchain with maximum reliability, it is completely free and it includes the transaction hash for later verification

Method 2: Portfolio tracking tools

Portfolio tracking tools such as DeBank or Zerion can display your history in a more visual way, although they have limitations for tax export. In our guide to tools for tracking cryptocurrencies we analyse the best options available.

DeBank:

1. Go to debank.com
2. Connect your wallet or paste your address
3. Go to the "History" section
4. You will see all your transactions across the supported networks

Zerion:

1. Go to zerion.io
2. Connect your Metamask
3. Navigate to "History"
4. View your multichain history

These tools have important limitations for tax use: they do not have a direct CSV export oriented to tax reporting, they do not calculate gains and losses according to the Spanish FIFO method, and they do not generate reports compatible with AEAT requirements.

Nevertheless, they offer advantages for visualization: they allow you to see your activity across multiple networks in a unified way, automatically identify the DeFi protocols you have interacted with, and are completely free

Method 3: Specialized tax tools (Koinly, CoinTracking)

Tax tools allow you to import your Metamask wallet and generate tax reports, although they require manual review to adapt them to Spanish regulations.

Koinly:

1. Create an account at koinly.io
2. Go to "Wallets" → "Add Wallet"
3. Select "Metamask" or "Ethereum Wallet"
4. Paste your public address
5. Koinly will automatically synchronize your history
6. Repeat for each network (Polygon, BSC, etc.)

CoinTracking:

1. Create an account at cointracking.info
2. Go to "Enter Coins" → "Import from Exchange"
3. Select "Blockchain Import" → "Ethereum"
4. Paste your address
5. Import the transactions

These tools present certain limitations for Spanish users: the reports labelled as "Spain" do not fully adapt to AEAT criteria, complex DeFi operations are often misclassified, they require a paid plan to export full reports and may need significant manual review and correction.

Despite this, they offer considerable advantages: they allow automatic multichain import, automatically calculate gains and losses, provide a visual interface for reviewing operations and allow export in multiple formats

Method 4: Specialized professional service

For users with complex operations or a high volume of transactions, a professional portfolio analysis service offers maximum accuracy and peace of mind.

This type of service includes manual review of every transaction, correct tax classification according to AEAT-specific criteria, precise application of the FIFO method in line with Spanish regulations, generation of reports ready to be submitted to the Tax Agency, and specialized support in case of potential requests from the Tax Agency

Let’s go through the detailed process to export your Metamask history using Etherscan, the most reliable method to obtain official blockchain data.

Prerequisites

Before you begin, make sure you have your Metamask wallet address (it starts with 0x...), a list of all the networks where you have operated, stable internet access, a spreadsheet application such as Excel or Google Sheets to consolidate data, and enough storage space for multiple CSV files

Step 1: Identify your wallet address

1. Open Metamask in your browser
2. Click on your account name (above the balance)
3. Your address will be copied automatically to the clipboard
4. Save this address: you will use it in all explorers

Step 2: Export transactions from Ethereum (Etherscan)

1. Go to etherscan.io
2. Paste your address in the search bar
3. You will see your wallet page with balance and transactions
4. Scroll down to the transactions table
5. Click on "Download CSV Export"
6. Select the date range (ideally from your first transaction)
7. Check "Txn Hash, Block, DateTime, From, To, Value"
8. Download and save as ETH_Transactions_2024.csv

Important: This basic export does not include:

• Internal transactions (contract-to-contract calls)
• ERC-20 token transfers
• NFT operations (ERC-721, ERC-1155)

Step 3: Export ERC-20 tokens (Etherscan)

1. On your Etherscan page, click on "Token Transfers (ERC-20)"
2. You will see all token transfers
3. Click on "Download CSV Export"
4. Select the same date range
5. Download and save as ETH_ERC20_Transfers_2024.csv

This file includes:

• Tokens received (DEX purchases, airdrops, rewards)
• Tokens sent (DEX sales, transfers)
• Token information (name, symbol, amount)

Step 4: Export internal transactions

1. On your Etherscan page, click on "Internal Txns"
2. These are contract-to-contract calls involving your wallet
3. Export as ETH_Internal_Txns_2024.csv

Why they are important:

Internal transactions include ETH received from contracts (rewards, staking withdrawals, swaps) that do not appear in the basic export.

Step 5: Repeat for other networks

If you have operated on Polygon, BSC or other networks, repeat steps 2–4 in each corresponding explorer:

Polygon (Polygonscan):

• URL: polygonscan.com
• Files: MATIC_Transactions.csv, MATIC_ERC20.csv

BSC (BscScan):

• URL: bscscan.com
• Files: BSC_Transactions.csv, BSC_BEP20.csv

Arbitrum (Arbiscan):

• URL: arbiscan.io
• Files: ARB_Transactions.csv, ARB_ERC20.csv

Step 6: Verify data completeness

Before continuing, verify that you have exported from all networks where you have activity, that the date range covers from your first operation to the present, that the CSV files open correctly without format errors, and that the number of transactions roughly matches what is shown in each blockchain explorer

Once the files are downloaded, you need to understand their structure to process them correctly.

Structure of the transactions CSV (Etherscan)

Identifying the type of operation

To classify each transaction for tax purposes, analyse the addresses:

If YOUR ADDRESS appears in "From":

• You sent ETH/tokens to another address
• It may be: internal transfer, payment, swap (sale)

If YOUR ADDRESS appears in "To":

• You received ETH/tokens
• It may be: own deposit, payment received, swap (purchase), airdrop

If the "To" address is a known contract:

• Uniswap router: DEX swap
• Aave/Compound contract: Lending operation
• Staking contract: Deposit or reward claim

Converting UTC dates to Spanish time

Etherscan exports all dates in UTC. For Spain:

• Winter time: UTC + 1 hour
• Summer time: UTC + 2 hours

This is crucial for operations close to year-end.

Example:

• Transaction in Etherscan: 2024-12-31 23:30:00 UTC
• Time in Spain (winter): 2025-01-01 00:30:00
• Tax year: 2025 (not 2024)

Calculating gas fee in EUR

To calculate the real cost of gas as a deductible expense:

1. Gas Fee in ETH = Gas × Gas Price / 1,000,000,000
2. Gas Fee in EUR = Gas Fee in ETH × ETH/EUR price at that time

Example:

• Gas Used: 150,000
• Gas Price: 30 Gwei
• ETH price: €2,500
• Gas Fee = 150,000 × 30 / 1,000,000,000 = 0.0045 ETH
• Gas Fee EUR = 0.0045 × €2,500 = €11.25

Mistake 1: Exporting only the Ethereum mainnet

Many users only export from Etherscan, forgetting they have also operated on Polygon, BSC, Arbitrum or other L2s. This leads to an incomplete tax history.

Solution:

• Check in Metamask all the networks you have configured
• Check your address in the explorer of each network
• Export from all networks where activity appears

Mistake 2: Not exporting ERC-20 token transfers

The basic Etherscan export only includes native ETH transactions. DEX swaps appear as ERC-20 token transfers that you must export separately.

Solution:

• Always export both "Transactions" and "Token Transfers (ERC-20)"
• Also export "Internal Txns" for complete capture

Mistake 3: Not treating swaps as taxable exchanges

Some users believe that exchanging ETH for USDC "is not a sale". Serious mistake: every swap between cryptocurrencies is an exchange that generates taxation.

Solution:

• Identify all DEX swap operations
• Calculate the gain/loss of each exchange
• Declare all exchanges even if they are crypto-to-crypto

Mistake 4: Forgetting airdrops and rewards

Tokens received from airdrops, staking rewards or yield farming must be declared at their market price at the time of receipt.

Solution:

• Review the "Token Transfers" column looking for tokens received without consideration
• Value each airdrop at the market price on the day of receipt
• Declare them as investment income

Mistake 5: Not keeping transaction hashes

The transaction hash is the irrefutable proof of each operation on the blockchain. Without it, you cannot prove to the Tax Agency the details of your operations.

Solution:

• Keep the original CSVs with all txhash values
• Save screenshots of important operations
• Never delete the original files

Mistake 6: Not converting values to EUR

The Tax Agency requires all operations to be declared in euros, at the exchange rate on the exact day and time of each operation.

Solution:

• For each operation, look up the EUR price of the cryptocurrency at that time
• Reliable sources: CoinMarketCap, CoinGecko, exchange data
• Document the source of each historical quotation

Once you have all the CSV files, you need to consolidate and process them to create your tax report.

Recommended folder structure

📁 Metamask_Fiscal_2024/
├── 📁 1_Original/
│   ├── 📁 Ethereum/
│   │   ├── 📄 ETH_Transactions_2024.csv
│   │   ├── 📄 ETH_ERC20_Transfers_2024.csv
│   │   └── 📄 ETH_Internal_Txns_2024.csv
│   ├── 📁 Polygon/
│   │   ├── 📄 MATIC_Transactions_2024.csv
│   │   └── 📄 MATIC_ERC20_Transfers_2024.csv
│   └── 📁 Arbitrum/
│       └── ...
├── 📁 2_Processed/
│   ├── 📄 All_Consolidated_Transactions.xlsx
│   ├── 📄 DEX_Swaps_with_EUR.xlsx
│   └── 📄 DeFi_Yields.xlsx
├── 📁 3_Evidence/
│   ├── 📄 Etherscan_Screenshots.png
│   ├── 📄 Historical_Prices.pdf
│   └── 📄 Internal_Movements_Proof.pdf
└── 📁 4_Final_Report/
    └── 📄 Metamask_Tax_Summary_2024.xlsx

Consolidation of operations

To create a complete tax report:

Step 1: Merge files by type

• Combine all transaction CSVs from different networks
• Combine all ERC-20/BEP-20 token CSVs
• Add a "Network" column to identify the source

Step 2: Remove duplicates

• Internal transactions may appear twice
• Use the txhash as a unique identifier
• Remove rows with duplicate txhash

Step 3: Classify by tax type

• Internal movement (non-taxable)
• Exchange/swap (capital gain)
• Receipt of yields (investment income)
• Payment with crypto (capital gain)
• Gas fees (deductible expense)

Step 4: Add EUR valuations

• For each operation, add columns with the EUR price
• Calculate the total EUR value of each transaction
• Sum gas fees converted to EUR

Calculating gains using the FIFO method

Spain requires the FIFO method. To calculate it with Metamask data:

Simplified example:

Operations:

1. 15/01/2024: You receive 1 ETH from Binance (purchased at €2,000)
2. 20/02/2024: Swap 0.5 ETH → 1,200 USDC (ETH trades at €2,400)
3. 15/03/2024: Swap 0.3 ETH → 900 DAI (ETH trades at €3,000)

FIFO calculation:

Operation 2 (Swap ETH→USDC):

• Sale price: 0.5 × €2,400 = €1,200
• Acquisition cost (FIFO): 0.5 × €2,000 = €1,000
• Capital gain: €200

Operation 3 (Swap ETH→DAI):

• Sale price: 0.3 × €3,000 = €900
• Acquisition cost (FIFO): 0.3 × €2,000 = €600
• Capital gain: €300

Total capital gains: €500

ETH remaining in portfolio:

• 0.2 ETH with an acquisition cost of €400 (0.2 × €2,000)

Tools to facilitate processing

If you have many operations, manual processing is complex. Some options:

Excel/Google Sheets:

• Import CSVs and use formulas to classify and calculate
• Create pivot tables to summarize by type of operation
• Use VLOOKUP (or XLOOKUP) to add historical quotations

Tax tools (Koinly, CoinTracking):

• Import wallet automatically
• Manual review of misclassified operations
• Report generation (requires adaptation to Spain)

Professional service:

• If your operations are complex (DeFi, multiple networks, high volume), a tax settlement service guarantees accuracy and peace of mind

Swaps on aggregators (1inch, Paraswap, Cowswap)

DEX aggregators split operations into multiple transactions to get a better price. This can cause confusion in the records.

How to identify them:

• Multiple token transfers in the same block
• Intermediate contract addresses
• The final amount received may differ from the expected one (due to slippage)

Solution:

• Group all transactions from the same swap (same txhash or consecutive block)
• Calculate the net value: tokens sent vs tokens received
• Treat the set as a single taxable exchange

Providing liquidity in pools (Uniswap, Curve)

When you deposit tokens in a liquidity pool:

1. Deposit: You send tokens A and B, receive LP tokens
2. Period: You accumulate fees proportional to your share
3. Withdrawal: You return LP tokens, receive tokens A' and B' (amounts different from the deposit)

Tax treatment:

• The deposit of tokens → Not taxable (similar to a deposit)
• Fees accumulated → Investment income
• Withdrawal with impermanent loss → Capital gain/loss

If you need specialized help with complex DeFi operations, our portfolio tracking service includes detailed analysis of positions in pools and protocols.

Bridging between networks

When you move tokens between networks (Ethereum → Polygon, for example):

Tax treatment:

• If the token is the same (ETH on Ethereum → ETH on Polygon): Non-taxable (internal movement)
• If there is a token conversion (ETH → WETH): technically it is an exchange, even if 1:1
• Bridge fees are deductible expenses

Required documentation:

• Transaction hash on the source network
• Transaction hash on the destination network
• Proof that both addresses belong to you

Liquid staking (Lido, Rocket Pool)

When you use liquid staking:

1. You deposit ETH, receive stETH (or rETH)
2. The stETH increases in value daily with rewards
3. When you sell stETH, you realize the accumulated gain

Tax treatment:

• The ETH deposit → Not taxable
• The increase in value of stETH → Realized when selling (capital gain)
• Alternative: Declare daily rewards as investment income

Airdrops and reward claims

Airdrops and rewards must be declared when you receive them:

Identification in CSVs:

• Token transfers where "From" is a contract and "To" is your wallet
• No corresponding outgoing transaction (not a swap)
• Significant amount of a new token

Valuation:

• Look up the token price at the exact time of the claim
• If the token has no quotation, value at €0 (declare when you sell it)
• Document the source of the quotation

Once all the data have been processed, prepare a structured report for your tax return.

Recommended executive summary

1. General information:

• Tax period: 01/01/2024 - 31/12/2024
• Wallets analysed: [your Metamask address]
• Networks included: Ethereum, Polygon, Arbitrum...
• Total operations: XXX transactions

2. Capital gains:

3. Investment income:

4. Deductible expenses (gas fees):

5. Balance as of 31 December:

(If it exceeds €50,000, you must file Form 721)

Supporting documentation

Keep for at least 4 years (preferably 6) all original CSV files from each explorer, screenshots of the export process, spreadsheets with processing and classification, sources of historical quotations used, the final tax report with detail for each operation, and evidence of internal movements proving your control over both addresses

Correctly exporting your Metamask history is more complex than doing it from a centralized exchange, but it is absolutely necessary for a correct tax return that complies with the AEAT.

Key points to remember

• ✅ Metamask has no native export: You must use blockchain explorers or specialized tools
• ✅ Export from ALL networks: Ethereum, Polygon, BSC, Arbitrum and any others where you have operated
• ✅ Types of export: Basic transactions, ERC-20 tokens and Internal Txns
• ✅ Each swap is a taxable exchange: Even crypto-to-crypto generates gain/loss
• ✅ Airdrops and rewards: Must be valued at the market price at the time of receipt
• ✅ Gas fees are deductible: Document all fees paid
• ✅ FIFO method is mandatory: First in, first out
• ✅ Keep evidence: Original CSVs, hashes, screenshots
• ✅ Convert to EUR: The Tax Agency requires all valuations in euros

Your next step

If you have exported your Metamask data but feel overwhelmed by the processing, classification of DeFi operations or calculation of the FIFO method, you are not alone.

At Cleriontax we specialize in cryptocurrency taxation and blockchain data analysis. Our team can process your Metamask history and generate a complete, verified tax report ready for your tax return.

Our services include:

• Import and consolidation of data from all your wallets and exchanges
• Detailed analysis of complex DeFi operations
• Correct tax classification according to AEAT criteria
• Precise application of the FIFO method
• Calculation of capital gains and investment income
• Complete tax report for Form 100
• Preparation of Form 721 if applicable
• Personalized tax advisory on optimization and planning
• Support in the event of requests from the Tax Agency

Do you have hundreds of DeFi operations on multiple networks? Our specialized methodologies process large volumes of blockchain transactions with precision.

Not sure you’ve exported everything correctly? We review your export, identify possible gaps and complete missing data.

Request your Metamask portfolio analysis

Comply with the Tax Agency without stress. Let the experts process your Metamask operations.

You may also be interested in: Visit our blog for more guides on cryptocurrency taxation, including our complete guide to exporting Binance history if you also operate on centralized exchanges.

Disclaimer: This article is for information and educational purposes only. It does not constitute personalized tax advice. Tax regulations are subject to change and each personal situation is unique. Always consult a professional tax advisor before making tax decisions. Cleriontax is not affiliated with Metamask or Consensys.

Last updated: December 2025

Published by: Cleriontax Team - Experts in Crypto Taxation and Data Analysis