evm-tx-debugger

To debug a failed EVM transaction, you decode input data, revert reasons, gas usage, and emitted events. This Skill translates low-level errors into human-friendly explanations and structured JSON reports to identify the exact failure point.

Yes, you can decode transaction input data and event logs across multiple chains. It supports Ethereum, BSC, Polygon, Arbitrum, Base, Optimism, and Avalanche using Blockscout and 4byte.directory lookups for multi-chain data.

The best way to profile gas usage is by evaluating the EIP-1559 breakdown and network comparison. This Skill provides detailed gas metrics and cost analysis to help you understand where gas was consumed before the transaction reverted.

To trace emitted events and reconstruct execution flow, you parse the transaction's event logs. This Skill interprens logs like Transfers, Approvals, and Swaps to build a narrative description of the multi-call interactions.

Contract deployment transactions fail due to issues detectable by analyzing input data and revert reasons. This Skill diagnoses failed contract deployments by decoding the execution details and returning structured error classifications.

Yes, you need to provide a specific transaction hash and the corresponding chain. This generates a complete debug report including the decode, error analysis, gas profile, and event narrative for the failed transaction.