Transaction Graph

WHAT IT DOES

Transaction Graph provides a visual and tabular exploration of any EVM wallet's on-chain activity. Enter an address or transaction hash, and the tool retrieves the native balance, transaction count, recent transaction history, and event logs emitted by contracts the address has interacted with. For addresses, it scans the last 5,000 blocks for logs, displaying contract events such as ERC-20 transfers, approvals, or custom contract emissions. For transaction hashes, it returns the transaction details, receipt status, gas usage, effective gas price, and any logs emitted during that specific transaction. The interface presents this data in a clean, sortable table format with clickable links to block explorers for deeper investigation. The tool is designed for quick forensic checks, debugging smart contract interactions, or simply understanding the activity pattern of a wallet.

HOW TO USE

Connect your EVM wallet using the Connect button in the header, or use the tool in read-only mode by pasting any address or transaction hash into the input field. Select the network that matches the address or transaction you are investigating from the Network dropdown—this ensures the correct RPC endpoint is used. Click Trace to begin the scan. For addresses, the tool will fetch the current balance, transaction count, and then scan recent blocks for event logs. A progress bar shows the log scan status, with chunking and automatic backoff to handle RPC rate limits gracefully. For transaction hashes, the tool fetches the transaction and receipt details, including any logs emitted. Results are displayed immediately in the results card, with block explorer links for every address and transaction.

THE TECHNICAL MECHANISM

The core differentiator of Transaction Graph is its adaptive log scanning engine. Public and even many private RPC endpoints enforce strict block range limits on eth_getLogs requests—some as low as 2,000 blocks, others 5,000 or 10,000. A naive implementation that requests logs for a 500,000-block range will fail immediately with an error indicating the range is too large, and the user sees nothing. Transaction Graph solves this by implementing a chunked scanning strategy that starts with a conservative chunk size (2,000 blocks) and dynamically halves the chunk size whenever a request is rejected for exceeding the limit. The scanner walks backward from the current block, fetching logs in overlapping chunks, and displays a progress indicator so the user can see the scan advancing. This approach ensures that the scan completes even when the underlying RPC provider imposes strict caps, without requiring the user to know or configure the provider's limits. Additionally, the tool uses the receipt.effectiveGasPrice field for cost calculations rather than tx.gasPrice, correctly handling EIP-1559 transactions where the gas price is a cap rather than the actual cost.

WHAT IT CANNOT SEE

Transaction Graph cannot fetch data from non-EVM chains such as Solana, Cosmos, Polkadot, or Bitcoin. It does not access mempool data or pending transactions—all displayed data is finalised on-chain. The log scanner is limited to the most recent 5,000 blocks to maintain performance and stay within RPC usage policies; for comprehensive historical analysis, you should use a dedicated blockchain explorer or archive node service. The tool cannot read private transaction data, decode custom contract events beyond the standard ERC-20/ERC-721 interfaces, or verify the current approval state—an Approval event log indicates a past approval, not that the approval still exists. Balance and transaction counts are accurate at the time of the request but may become stale immediately after due to new blocks being produced. The tool is rate-limited by the underlying RPC provider; during peak usage or with free tier RPC endpoints, requests may be throttled.

PLEASE NOTE

This tool is EVM-only and requires the BotGentz extension framework to be installed. It is read-only and does not sign or send any transactions. All data is fetched directly from the RPC endpoint associated with the selected network; no data is stored or transmitted to any external server. For networks not listed in the dropdown, you can use the custom network option by pasting your own RPC URL (if your BotGentz build supports it). This tool is free to use and is intended for informational and debugging purposes only.