Wallet History Exporter

WHAT IT DOES

Wallet History Exporter reads the user's current wallet address and network chain ID from the connected wallet, reads transaction history for the specified address via eth_getLogs and eth_getTransactionCount, reads transaction details via eth_getTransactionByHash, reads block timestamps via eth_getBlockByNumber, and optionally reads token transfer events via ERC-20 Transfer event logs. The tool takes any Ethereum address and retrieves its complete transaction history, including native ETH transfers and ERC-20 token transfers. It displays the transactions in a sortable list with hash, destination, value, and timestamp, and provides a CSV export function for further analysis. The tool automatically handles pagination and chunked requests to work around provider RPC limits.

HOW TO USE

Connect your existing wallet using the "Connect" button — this establishes the wallet bridge and displays your current address and chain ID. Enter any Ethereum address into the input field and select the number of transactions to fetch (10, 25, 50, 100, or 200). Click "Fetch History" — the tool retrieves the transaction count for the address via eth_getTransactionCount, then uses eth_getLogs with chunked backoff to fetch all transaction hashes. It then fetches each transaction's details via eth_getTransactionByHash and block timestamps via eth_getBlockByNumber. Results are displayed in a table showing transaction hash (clickable to Etherscan), destination address, ETH value, and timestamp. Click "Export CSV" to download the transaction history as a CSV file for use in spreadsheets or external analysis tools.

MECHANISM — CHUNKED LOG SCANNING WITH AUTOMATIC BACKOFF

This tool uses a chunked log scanning approach with automatic backoff to handle the varying eth_getLogs limits across different RPC providers. The system first fetches the transaction count for the address via eth_getTransactionCount to determine the total number of transactions. It then scans logs using eth_getLogs with a configurable chunk size (starting at 2000 blocks). If a request fails due to provider limits, the tool automatically halves the chunk size and retries (backing off up to 5 times), ensuring that a single refusal does not end the scan. Once all transaction hashes are collected, the tool fetches each transaction's details and block timestamps, then displays the results. This approach works reliably across different providers without hardcoding block range limits. The tool also supports ERC-20 Transfer event logs for comprehensive transaction history.

WHAT IT CANNOT SEE

This tool cannot fetch transaction history for addresses on non-EVM chains. It cannot retrieve transaction history beyond what the provider's eth_getLogs limits allow without chunking and backoff. It cannot guarantee that all historical transactions are retrievable if the provider has pruning or retention limits. It cannot read private transaction data or decrypt transaction inputs. It cannot detect off-chain activity or transactions on private networks. It cannot export data in formats other than those provided. It cannot reconstruct the full state of the wallet at any point in time. It cannot fetch transaction history for addresses that have never transacted. It cannot handle very large transaction histories without rate limiting or pagination.

PLEASE NOTE

EVM chains only — supports Ethereum mainnet and all EVM-compatible networks. This tool requires a real EVM wallet extension (such as MetaMask) to provide a provider for reading on-chain data. The tool is read-only and never signs or broadcasts transactions. Transaction history is limited by the provider's eth_getLogs capabilities; for very old transactions, you may need to use a dedicated archival node or blockchain explorer API.