Table of Contents
The Question: How To Recover Transaction History When Pool Tracking Disappears

Your yield position paid 8.3% for nine months. It generated 47 taxable distributions. The pool dropped from DefiLlama and Zapper last week. Tax filing is in six days. The protocol dashboard returns a 404. You need a complete transaction record or you file with zero cost basis and pay tax on gross proceeds instead of net gain.
The income mechanism is simple. Missing transaction records during tax season force conservative cost basis assumptions. If you deposited $50,000 and withdrew $54,150, the IRS sees $54,150 in proceeds. Without deposit records, your cost basis is zero. You pay tax on $54,150 instead of $4,150. At 32% marginal rate, that is $17,328 instead of $1,328. The difference is $16,000 in overpaid tax.
Block explorers, protocol subgraphs, and wallet transaction exports reconstruct complete position history without protocol cooperation. The data persists on-chain regardless of UI availability. Here is the recovery process.
Block Explorer Transaction Pull: Etherscan and Solscan API Methods

Block explorers index every transaction your wallet executed. The data includes deposits, withdrawals, claims, and token transfers. Etherscan covers EVM chains. Solscan covers Solana. Both offer free CSV export and API access.
The Etherscan CSV export process:
- Navigate to etherscan.io and enter your wallet address in the search field.
- Scroll to the bottom of the transactions page.
- Select "Download CSV Export" and choose the transaction type: normal transactions, internal transactions, or ERC-20 token transfers.
- Download all three files if the position involved deposits (normal), yield claims (internal), and token movements (ERC-20).
The free tier CSV export includes date, transaction hash, sender, receiver, token quantity, and gas cost. This satisfies the minimum requirements for tax software import: date, amount, currency, transaction type, and fee.
The Etherscan API method provides programmatic access for wallets with more than 1,000 transactions. As of July 1, 2026, the free tier returns a maximum of 1,000 records per request. Wallets exceeding that limit require pagination or a paid tier subscription. The Standard plan costs $199 per month and allows 10 calls per second across all major EVM chains using a single API key.
The API endpoint for transaction history:
https://api.etherscan.io/api?module=account&action=txlist&address=YOUR_WALLET_ADDRESS&startblock=0&endblock=99999999&sort=asc&apikey=YOUR_API_KEY
Replace YOUR_WALLET_ADDRESS with the wallet address that held the position. Replace YOUR_API_KEY with the key obtained from Etherscan's API documentation. The response returns JSON formatted transaction data including timestamp, gas cost, input data, and transaction status.
For ERC-20 token transfers, change the action parameter to tokentx:
https://api.etherscan.io/api?module=account&action=tokentx&address=YOUR_WALLET_ADDRESS&startblock=0&endblock=99999999&sort=asc&apikey=YOUR_API_KEY
Solscan uses a similar structure for Solana wallets. The free tier includes basic transaction history. The Pro API starts at $49 per month for 20 million monthly compute units, with each endpoint call consuming 100 CU. The endpoint format:
https://pro-api.solscan.io/v1.0/account/transactions?account=YOUR_WALLET_ADDRESS
Include your API key in the request header as token: YOUR_API_KEY. The response includes transaction signatures, block time, instruction data, and token movements decoded into human-readable format.
Multi-chain positions require separate API calls for each chain. Ethereum mainnet uses api.etherscan.io. Arbitrum uses api.arbiscan.io. Base uses api.basescan.com. Etherscan V2 consolidates these under a single API key, but the endpoint URLs remain chain-specific. Cross-protocol yield strategies that touch Ethereum, Polygon, and Arbitrum generate three separate CSV files that must be merged chronologically before import.
Protocol Subgraph Query: GraphQL Templates For Pool-Specific Data

Block explorers return raw transaction data. Protocol subgraphs return decoded position data: liquidity added, fees earned, impermanent loss, and pool share percentage. The Graph is a decentralized indexing protocol that indexes DeFi data and exposes it via GraphQL queries. Uptime exceeds 99.99%.
Not all protocols maintain active subgraphs after delisting pools. Uniswap, Curve, Aave, and Compound maintain long-term subgraph availability. Smaller protocols may deprecate subgraphs when pools lose liquidity. The fallback is raw block explorer data.
The Uniswap V3 subgraph query template for position history:
{
positions(where: {owner: "YOUR_WALLET_ADDRESS"}) {
id
pool {
token0 {
symbol
}
token1 {
symbol
}
}
liquidity
depositedToken0
depositedToken1
withdrawnToken0
withdrawnToken1
collectedFeesToken0
collectedFeesToken1
}
}
Replace YOUR_WALLET_ADDRESS with the wallet address in lowercase. The query returns position ID, token pair, deposited amounts, withdrawn amounts, and collected fees. This decomposes the yield into principal and income components required for accurate cost basis calculation.
The Graph Studio gateway bills queries by compute usage. Simple position queries consume minimal resources. Pool state queries for large liquidity pools may require multiple calls. Uniswap V3 pools with more than 1,000 initialized ticks require pagination to fetch complete state.
The Curve pool query template for yield position history:
{
liquidityPositions(where: {user: "YOUR_WALLET_ADDRESS"}) {
id
pair {
token0 {
symbol
}
token1 {
symbol
}
}
liquidityTokenBalance
historicalSnapshots {
timestamp
liquidityTokenBalance
liquidityTokenTotalSupply
reserve0
reserve1
}
}
}
The historical snapshots array includes time-series data showing liquidity balance and pool reserves at each snapshot. This reconstructs the position value over time, including appreciation and depreciation from pool ratio changes.
Aave lending position query:
{
userReserves(where: {user: "YOUR_WALLET_ADDRESS"}) {
id
reserve {
symbol
}
currentATokenBalance
currentTotalDebt
liquidityRate
stableBorrowRate
variableBorrowRate
}
}
The query returns deposited balance (currentATokenBalance), accrued interest (derived from liquidityRate), and borrowed amounts if applicable. The liquidityRate is expressed in ray units (1e27). Divide by 1e27 and multiply by 100 to convert to percentage APY.
When a protocol subgraph is unavailable, the fallback method is raw transaction log filtering. Etherscan's advanced filter allows filtering by contract address and event topic. Deposit events, withdrawal events, and claim events each emit specific log topics that can be isolated and exported.
Wallet Statement Reconstruction: Combining Multi-Source Data
Block explorer CSVs provide raw transactions. Subgraph queries provide decoded position data. Tax software requires a unified chronological record with standardized field names. The reconstruction process merges data sources and formats them for import.
The required CSV fields for most tax software:
- Date (YYYY-MM-DD format or MM/DD/YYYY depending on software)
- Transaction Type (deposit, withdrawal, income, trade)
- Token Quantity (numerical value)
- Token Symbol (USDC, ETH, WBTC, etc.)
- Transaction ID (transaction hash from block explorer)
- Fee (gas cost in native token)
The transaction type classification determines tax treatment. Deposits and withdrawals of the same token are non-taxable transfers. Yield claims, fee collections, and reward distributions are taxable income at fair market value on the date received. Token swaps within the position (trading earned fees from ETH to USDC) are taxable dispositions with capital gain or loss calculation.
The assembly process for a Uniswap V3 ETH-USDC position:
- Download Etherscan ERC-20 token transfer CSV for the wallet address.
- Run the Uniswap V3 subgraph query to retrieve position deposits, withdrawals, and collected fees.
- Cross-reference transaction hashes between the CSV and the subgraph results to identify which transactions correspond to the specific pool.
- Create a new spreadsheet with columns: Date, Type, Token, Quantity, Transaction Hash, Fee.
- Populate deposit rows using the depositedToken0 and depositedToken1 values from the subgraph.
- Populate withdrawal rows using the withdrawnToken0 and withdrawnToken1 values.
- Populate income rows using the collectedFeesToken0 and collectedFeesToken1 values, marking them as taxable income.
- Add gas fees from the Etherscan CSV to each row.
Multi-chain positions require separate CSV assembly for each chain, then chronological merge. If the same wallet held USDC on Ethereum, Polygon, and Arbitrum in three separate pools, download three Etherscan-equivalent CSVs (Etherscan, Polygonscan, Arbiscan), format each identically, then combine them sorted by date ascending.
The combined file must deduplicate any transactions that appear in multiple data sources. Cross-chain bridge transactions appear in both the origin chain and destination chain explorers. Mark bridge transactions as transfers rather than taxable events unless the bridge involved a token swap.
TXF (Tax Exchange Format) is the preferred standardized format for import into Koinly, CoinTracking, and other dedicated crypto tax tools. TurboTax dropped CSV support for crypto in January 2026. TurboTax no longer calculates cost basis from raw exchange data. Use a dedicated crypto tax tool to generate the final tax forms rather than attempting direct import into general tax software.
Third-Party Archive Tools: Recovery When Primary Sources Fail
Block explorers occasionally fail to index early transactions on newly launched chains. Protocol subgraphs may be deprecated. Third-party archive tools maintain historical snapshots independent of protocol maintenance.
Dune Analytics maintains indexed blockchain data with custom SQL query capability. The free tier allows unlimited queries with rate limits. The query editor supports filtering by wallet address, contract address, and date range. Dune tables include decoded event logs for major DeFi protocols.
The Dune SQL query template for Uniswap V3 positions:
SELECT
evt_block_time AS date,
owner AS wallet_address,
amount0,
amount1,
liquidity,
evt_tx_hash AS transaction_hash
FROM uniswap_v3_ethereum.Pool_evt_Mint
WHERE owner = 'YOUR_WALLET_ADDRESS'
ORDER BY evt_block_time ASC
Replace YOUR_WALLET_ADDRESS with the wallet in lowercase. The query returns mint events (deposits) with token amounts and liquidity values. Similar queries exist for burn events (withdrawals) and collect events (fee claims).
DeBank and Zapper maintain historical wallet snapshots. The DeBank API returns position history including entry date, exit date, and realized profit. The API is free for personal use with rate limits. The endpoint format:
https://openapi.debank.com/v1/user/all_history_list?id=YOUR_WALLET_ADDRESS
The response includes protocol name, token symbols, action type (deposit, withdraw, claim), and USD value at the time of transaction. This provides a high-level summary useful for cross-checking against detailed block explorer data.
Zerion offers similar historical position tracking. The free tier includes transaction history export. The dashboard displays all historical positions with entry and exit prices. The CSV export includes taxable income events flagged separately from principal movements.
When all primary and third-party sources fail to reconstruct a complete position history, the final method is manual transaction reconstruction from wallet transaction lists. MetaMask, Coinbase Wallet, and Ledger Live maintain local transaction logs. Export the wallet transaction history from the wallet software, filter by date range corresponding to the position duration, and manually categorize each transaction by cross-referencing the contract address with the protocol's known contract addresses.
Tax Software Import Format: CSV Structure and Transaction Categorization
Tax software expects standardized transaction categorization. The same on-chain event may map to different tax treatments depending on context. A token transfer out of a wallet is a sale if it goes to an exchange, a non-taxable transfer if it goes to another wallet you control, or a gift if it goes to a third party.
The standard transaction type categories:
- Deposit: Moving tokens into a protocol or pool, non-taxable.
- Withdrawal: Removing tokens from a protocol or pool, non-taxable unless combined with a sale.
- Income: Receiving yield, fees, or rewards, taxable as ordinary income at fair market value on receipt date.
- Trade: Swapping one token for another, taxable as capital gain or loss.
- Transfer: Moving tokens between wallets you control, non-taxable if properly documented.
Yield claims from liquidity provision are taxable income. The taxable amount is the fair market value in USD of the tokens received on the date of the claim transaction. If the claim transaction collected 0.5 ETH in fees and ETH traded at $3,200, the taxable income is $1,600.
Auto-compounding positions create phantom income events. If the protocol automatically reinvests earned fees back into the pool, the reinvestment is a taxable income event followed by a non-taxable deposit. The position balance increases without a withdrawal transaction, but the IRS treats the earned fees as income. The subgraph query must decompose the balance increase into the income component and the reinvested component.
The CSV row format for a fee claim event:
2025-11-15, Income, 0.5, ETH, 0xabc123..., 0.002
Translation: On November 15, 2025, the wallet received 0.5 ETH as income, documented by transaction hash 0xabc123, with 0.002 ETH paid in gas fees. The tax software calculates the USD value using the ETH price on that date.
The CSV row format for a deposit event:
2025-08-10, Deposit, 10000, USDC, 0xdef456..., 0.003
Translation: On August 10, 2025, the wallet deposited 10,000 USDC, documented by transaction hash 0xdef456, with 0.003 ETH paid in gas fees. This establishes cost basis for the position.
Import the completed CSV into Koinly, CoinTracking, or CoinLedger. The software matches deposits and withdrawals to calculate holding periods, applies the appropriate tax rate to income events, and generates IRS Form 8949 for capital gains and Schedule 1 for ordinary income. The software does not automatically capture multi-protocol position migrations or complex DeFi strategies involving wrapped tokens, so manual review of the generated forms is required.
When Block Explorer Recovery Fails: Edge Cases and Stress Conditions
The recovery methods above assume the pool contract is known, the wallet address is known, and the transaction history is indexed. Three edge cases break this assumption.
First, the wallet used a contract wallet or smart wallet with delegated transaction signing. Gnosis Safe, Argent, and Authereum wallets execute transactions through proxy contracts. The block explorer shows transactions originating from the proxy contract, not the user's address. The recovery method is to query the proxy contract address instead of the user address, then filter results by the user's authorized signer address in the transaction input data.
Second, the pool contract was upgraded or migrated during the position duration. Curve pools occasionally migrate to new contracts. Uniswap V2 pools migrated to V3. The position history spans two contract addresses. Query both contracts separately, then merge the results chronologically. The subgraph query must include both the old pool address and the new pool address in the WHERE clause.
Third, the chain was an L2 or sidechain with incomplete block explorer indexing. Early Arbitrum and Optimism transactions occasionally failed to index on Arbiscan and Optimistic Etherscan. The fallback is to run a local archive node and query the chain state directly, or use a third-party RPC provider like QuickNode that maintains historical state. This requires technical capability beyond most users. The alternative is to reconstruct the position from wallet transaction logs and protocol dashboard screenshots if available.
Rate Limiting and API Cost Management During Recovery
High-volume wallets hit Etherscan rate limits during bulk transaction export. The free tier allows 5 calls per second with a 100,000 daily call limit. A wallet with 5,000 transactions requires 5 paginated API calls at 1,000 records each. A wallet with 50,000 transactions requires 50 calls. At 5 calls per second, that is 10 seconds of API usage.
The rate limit resets daily. If the recovery process exceeds the daily limit, wait 24 hours or upgrade to a paid tier. The Lite plan ($49/month) allows 5 calls per second with no daily cap. The Standard plan ($199/month) allows 10 calls per second and includes all major EVM chains under a single API key.
Subgraph queries on The Graph are billed by compute usage. Simple position queries consume negligible resources. Pool state queries for high-liquidity pools with thousands of LPs may exceed free tier limits. The Graph Studio provides a billing dashboard showing query cost in GRT tokens. Budget approximately $5-20 in GRT for comprehensive historical queries across multiple protocols.
Solscan Pro API billing is flat-rate per endpoint call. Each call consumes 100 compute units regardless of response size. The Lite plan includes 20 million monthly CU, sufficient for 200,000 endpoint calls. A wallet with 10,000 Solana transactions requires approximately 100 API calls to retrieve complete history, consuming 10,000 CU.
The Takeaway: Recovery Works When You Act Within 72 Hours
Position history persists on-chain regardless of UI availability. Block explorer CSV export provides complete transaction records for wallets under 1,000 transactions. API access with pagination handles larger wallets. Protocol subgraphs decode position-specific data including deposits, withdrawals, and fee collections. Third-party archive tools fill gaps when primary sources fail.
The recovery process must start within 72 hours of discovering the pool dropped from tracking. Subgraph availability degrades over time as protocols deprecate indexing infrastructure. Block explorers rarely lose historical data, but API endpoint formats change. Wallet dashboard providers cache transaction history for 90 days before requiring re-sync.
The specific stress condition that breaks recovery is waiting until the week before tax filing. Protocol teams do not respond to transaction history requests during tax season. Subgraph endpoints may be offline. API rate limits prevent bulk export under time pressure. Reconstruct position history when the pool disappears, not when the tax deadline arrives.
The on-chain verification is transaction hash matching. Every deposit, withdrawal, and claim event has a unique transaction hash. Cross-reference the hash between block explorer data, subgraph results, and wallet logs. If all three sources return the same hash for a transaction, the record is accurate. If sources conflict, the block explorer is authoritative. The blockchain does not lie. The UI might.
Frequently Asked Questions
Can I recover transaction history if the protocol website is completely offline?
Yes. Transaction history persists on-chain regardless of protocol website availability. Use block explorers like Etherscan or Solscan to export your wallet's complete transaction log. The data includes all deposits, withdrawals, and claims executed by your wallet address. Protocol subgraphs maintained by The Graph provide decoded position data even when the protocol dashboard is offline. Third-party tools like Dune Analytics, DeBank, and Zerion maintain independent historical snapshots. The blockchain records every transaction permanently.
What is the difference between block explorer CSV export and subgraph queries?
Block explorer CSV export provides raw transaction data: transaction hash, sender, receiver, token amount, gas cost, and timestamp. This includes every transaction your wallet executed. Subgraph queries provide decoded protocol-specific data: liquidity deposited, fees earned, impermanent loss, and pool share percentage. Subgraphs interpret the raw transaction data in the context of the specific protocol. For tax filing, you need both. Block explorer data establishes the chronological record. Subgraph data decomposes yield into principal and income components required for accurate cost basis calculation.
How do I handle positions that span multiple chains like Ethereum and Arbitrum?
Query each chain separately using chain-specific block explorers. Ethereum uses etherscan.io, Arbitrum uses arbiscan.io, Polygon uses polygonscan.com. Download the CSV export or run API calls for each chain. Create separate spreadsheets with identical column structures, then merge them chronologically by date. Cross-chain bridge transactions appear on both chains. Mark these as transfers rather than taxable events unless the bridge involved a token swap. Etherscan V2 API allows one key across chains but requires separate endpoint calls per chain.
What happens if my wallet has more than 1,000 transactions and I hit the free tier limit?
Use pagination to retrieve records in batches of 1,000. Etherscan API accepts startblock and endblock parameters to specify the block range for each request. Make multiple calls incrementing the block range until you retrieve all transactions. The free tier allows 100,000 calls per day, sufficient for wallets with up to 100 million transactions theoretically. Practically, rate limits of 5 calls per second mean 1,000 calls takes 200 seconds. If you need faster retrieval, upgrade to Etherscan Lite ($49/month) or Standard ($199/month) for higher rate limits and no daily cap.
Can I use this method to recover positions from protocols that completely shut down?
Yes, with one limitation. Block explorer data persists indefinitely as long as the blockchain itself operates. You can retrieve transaction history from defunct protocols years after shutdown. Protocol subgraphs may be deprecated when teams stop maintaining indexing infrastructure. If the subgraph is offline, fall back to raw block explorer transaction logs and filter by the protocol's contract address. The contract address never changes even after protocol shutdown. Etherscan's advanced filter allows isolating transactions by contract address and event topic to reconstruct position history manually.
Koinly imports from 800+ exchanges and wallets and handles the DeFi cases most tools get wrong - rebasing tokens, LP positions, staking rewards.
Try KoinlyWe may earn a commission if you sign up through this link, at no cost to you. It does not change what gets recommended.
You just received block explorer, subgraph, and CSV assembly methods that reconstruct disappeared position history. Those pools will drop from tracking again next quarter.
Every Thursday: where crypto yield actually is - stablecoins, liquid staking and DeFi lending, with the risk named next to the rate and what changed since last week.
Get it free every ThursdayFree. No trade calls, no allocations, no hype. Unsubscribe in one click.