Transaction Decoder

Explain This Tx

Get human-readable explanations of complex Ethereum transactions. Break down function calls, state changes, and event logs.

Transaction Decoder (Human Readable)

Transaction Hash

Transaction Explanation & Decoder

Understand the inner workings of Ethereum transactions. Decode input data, analyze state changes, and debug failed transactions with our human-readable explorer.

What is Transaction Decoding?

Every interaction on Ethereum is recorded as a hexadecimal string. Decoding this string usually requires the contract's ABI (Application Binary Interface). This tool automatically fetches ABIs to translate raw hex (e.g., `0xa9059cbb...`) into readable function calls (e.g., `transfer(to, amount)`).

Anatomy of a Transaction

Nonce: A counter to prevent replay attacks.
Gas Limit: Maximum computation allowed.
Value: Amount of ETH sent.
Data: The payload (function signature + parameters) for smart contract calls.
v, r, s: Cryptographic signature components proving the sender's identity.

Debugging Failed Transactions

Transactions often fail due to "Out of Gas" or "Reverted" errors. A revert usually provides a reason string (e.g., "Slippage tolerance exceeded"). Decoding the input data helps identify exactly which parameters caused the contract to reject the transaction.

Frequently Asked Questions

Input Data is a hex field attached to a transaction. For simple ETH transfers, it's empty. For contract interactions, it contains the function signature (first 4 bytes of the hash) and encoded arguments.

Most verified contracts publish their ABI on Etherscan. Our tool automatically attempts to fetch this for you. If a contract is unverified, decoding the specific function input is much harder without guessing.

This is a custom error thrown by the smart contract. You can often decode this error hash using a database of known error signatures (like 4byte.directory) to find out the human-readable reason (e.g., 'InsignificantOutputAmount').

Yes! Since most chains (BSC, Polygon, Optimism, Arbitrum) are EVM-compatible, the decoding logic is identical. You just need the ABI specific to the contract on that chain.

Logs (Events) are how smart contracts communicate to the outside world. They are cheaper to store than contract state. Tokens transfers, swaps, and NFT mints are all tracked via `Transfer` events emitted in the logs.

Loading...