Failed Transaction Rate Monitor

WHAT IT DOES Failed Transaction Rate Monitor is a read-only developer tool that monitors the success and failure rates of transactions interacting with EVM smart contracts. It reads transaction receipts via eth_getTransactionReceipt for a range of recent transactions, calculates the percentage of failed transactions, compares the failure rate against a user-defined threshold, and provides detailed statistics including total transactions, successes, failures, and the failure rate percentage. The tool helps developers identify contract health issues, detect bugs or misconfigurations causing transaction reverts, and monitor the stability of deployed contracts over time. HOW TO USE Connect your EVM-compatible wallet via the BGWallet bridge and select the network where your contract is deployed. Enter the contract address (optional—leave blank to monitor all transactions), the number of recent transactions to analyze (10-200), and an alert threshold percentage (1-100%). Click "Monitor Failure Rate" to fetch transaction receipts and calculate statistics. Results include total transactions analyzed, success and failure counts, the failure rate percentage, a visual progress bar showing the failure rate relative to the threshold, a status indicator (Normal, Elevated, or Alert), detailed recommendations, and a list of recent failed transactions with block numbers, sender/recipient addresses, and transaction hashes. The tool also provides an alert stub for threshold breaches. All analysis is read-only—no signatures or transactions are submitted. TECHNICAL MECHANISM The tool uses ethers.js v5.7.2 to fetch transaction data via the provider. If a contract address is provided, it uses chunked eth_getLogs fetching (automatically halving block ranges when RPC providers reject full-range requests) to retrieve logs and extract transaction hashes, then fetches receipts for each hash. If no contract address is provided, it scans recent blocks (up to 500 blocks) and fetches transaction receipts directly. Each receipt's status field (1 = success, 0 = failure) is checked, and failures are counted. The failure rate is calculated as (failed_transactions / total_transactions) * 100. The tool compares the failure rate against the user-defined threshold and generates a severity assessment: Normal (100% of threshold). The tool also provides a list of recent failed transactions with contextual metadata and generates actionable recommendations based on the severity. The alert stub provides a placeholder for integration with external notification systems. WHAT IT CANNOT SEE This tool has fundamental limitations that users must understand. It cannot actually send alerts or notifications—the tool provides an alert stub but requires external infrastructure for actual notifications. It cannot determine the root cause of failures without analyzing revert reasons or simulation—the tool only detects that a transaction failed, not why. It cannot distinguish between legitimate reverts (e.g., expected validation failures) and bugs without context—the tool treats all failures equally. It cannot monitor transactions that are not submitted through the RPC provider—the tool only analyzes on-chain transactions. It cannot detect failures that occur off-chain or in private mempools. It cannot predict future failure rates or trends—the tool only provides historical analysis. It cannot analyze failures that occur without a receipt (e.g., transactions that are dropped). It cannot provide function-level failure breakdowns without ABI decoding—the tool only provides aggregate statistics. The tool's alert stub is a placeholder for demonstration purposes. PLEASE NOTE This tool only supports EVM-compatible blockchains (Ethereum, Polygon, BSC, Avalanche C-Chain, Optimism, Arbitrum, and their testnets). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool is free, open-source, requires no API keys, and uses the wallet's native provider for all read operations. For production alerting, integrate the tool's output with external notification systems.