Check Wallet Transaction History

WHAT IT DOES

This tool connects to your MetaMask wallet and fetches your transaction history from the blockchain. It scans a configurable range of recent blocks, extracting all transactions involving your wallet address — incoming transfers, outgoing sends, and contract interactions. The tool uses a chunked scanning approach that automatically halves chunk sizes when it hits RPC limits, ensuring it works reliably across different providers. Results are displayed in a clean list showing transaction hashes, direction (in/out/contract), value, status (success/failed/pending), timestamps, and counterparty addresses. Click any transaction hash to view it on the block explorer.

HOW TO USE

Connect your MetaMask wallet using the Connect button. Enter the number of recent blocks to scan (default 1000) — larger values find more transactions but take longer. Click "Fetch History" to start scanning. The tool will show progress as it scans blocks in chunks. Once complete, your transactions will appear in a list sorted by block number (newest first). The list shows outgoing transactions (you sent), incoming transactions (you received), and contract interactions. Use the block explorer link (click the hash) to view full transaction details.

TECHNICAL MECHANISM

The tool uses the BGWallet bridge to access the blockchain provider via ethers.js. It implements a robust chunked scanning strategy to handle varying RPC eth_getLogs limits. Starting from the current block, it works backwards in configurable chunks (default 500 blocks). When the RPC returns a "limit exceeded" error, the tool halves the chunk size and retries the same range — this continues until the chunk is small enough to succeed, ensuring scanning completes even on restrictive providers. For each chunk, it calls eth_getLogs with the wallet address as the filter, then fetches full transaction details and receipts for each hash found. It also attempts to fetch block timestamps for accurate time display. The tool deduplicates transactions by hash and sorts them chronologically.

WHAT IT CANNOT SEE

This tool cannot read transaction history beyond the RPC provider's block range limits. It cannot read transaction history for addresses that have not been connected or are not the current active wallet. It cannot read transaction history from non-EVM networks like Solana, Bitcoin, or Tron. It cannot decode custom contract interactions without the contract ABI — contract calls are shown but not human-readable. It cannot display internal transactions or traces (e.g., transfers triggered by smart contract execution). It cannot provide transaction history for wallets that are not the connected wallet. It cannot detect transactions that were sent from an address but not logged due to node pruning or archive node requirements. It cannot show pending transactions that have not been included in a block.

PLEASE NOTE

This tool works only with EVM-compatible wallets connected via the BGWallet bridge. The scanning range is limited by the RPC provider's eth_getLogs capabilities — some providers limit the range to as little as 10,000 blocks. The chunked halving strategy ensures scanning completes even on restrictive providers, but may take longer. Transaction history for very old transactions may not be available if the provider does not maintain full history. The tool does not store or transmit any data — all processing occurs in your browser. This tool is provided as a viewer utility and does not provide advanced analytics, filtering, or export functionality. For comprehensive transaction history, consider using a block explorer or dedicated portfolio tracker.