evm-tx-debugger

Decode EVM transaction failures with revert reasons, gas metrics, and event narratives.

17|45|Updated Jan 23, 2026

Search Tags:#evm #event-logs #blockscout #transaction-debugging #revert-reason #gas-profile #4byte-directory

Ready to run

npx skills add https://github.com/XSpoonAi/spoon-awesome-skill --skill evm-tx-debugger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evm-tx-debugger
Source: https://github.com/XSpoonAi/spoon-awesome-skill/tree/main/enterprise-skills/debugging/evm-tx-debugger
Command: npx skills add https://github.com/XSpoonAi/spoon-awesome-skill --skill evm-tx-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Decode and explain failed EVM transactions by automatically decoding input data, revert reasons, gas usage, and emitted events, delivering actionable debug insights.

Core Features & Use Cases

Automatic transaction decode: identify the called method, parameters, and involved contracts across multiple chains.
Revert reason decoding and error classification: translate low-level errors into human-friendly explanations and fixes.
Gas profiling and cost analysis: evaluate gas usage, EIP-1559 breakdown, and network comparison to optimize costs.
Event parsing: interpret logs and events to reconstruct the execution flow (e.g., Transfers, Approvals, Swaps).

Quick Start

Provide a transaction hash and chain to generate a complete debug report that includes a decode, error analysis, gas profile, and event narrative.

Frequently Asked Questions about evm-tx-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug a failed EVM transaction and find the revert reason?▼

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.

Can I decode transaction input data and event logs across multiple chains like Arbitrum and Polygon?▼

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.

What is the best way to profile gas usage and analyze EIP-1559 costs for a failed trade?▼

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.

How do I trace emitted events and logs to reconstruct a complex multi-call execution flow?▼

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.

Why does my contract deployment transaction fail and how can I analyze it?▼

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.

Do I need a transaction hash and chain to start diagnosing EVM transaction failures?▼

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.