Skip to content
Handy Browser Tools

Ethereum Transaction Decoder

Paste a raw signed transaction (the 0x-hex you'd broadcast with eth_sendRawTransaction) and see every field decoded: nonce, gas, recipient, value, calldata, chain id and signature. The sender address is recovered from the signature, and legacy, EIP-2930, EIP-1559, EIP-4844 and EIP-7702 transactions are all supported.

Private by default: processing stays on your device
RAW TRANSACTION

Paste a signed transaction hex

Try:

Decoding is offline and read-only — nothing is broadcast.

Every field, decoded.

Type, sender, value, gas, access lists and signature.

Decoded fields will appear here once you paste a transaction.

Good to know

Supports legacy, EIP-2930, EIP-1559, EIP-4844, and EIP-7702 transactions. The sender address is recovered purely from the signature — no network lookup.

Example: EIP-155 legacy transfer

Input

0xf86c098504a817c800825208943535353535353535353535353535353535353535880de0b6b3a76400008025a028ef61340bd939bc2195fe537567866003e1a15d3c71ff63e1590620aa636276a067cbe9d8997f761aecb703304b3800ccf555c9f3dc64214b297fb1966a3b6d83

Output

From 0x9d8A…5A4F → 0x3535…3535, value 1 ETH, nonce 9, chain id 1
Share this page X LinkedIn Reddit

These buttons share the page link, not your input.

Frequently asked questions

What is a raw transaction?

It's the RLP-serialized, signed transaction bytes, the exact hex you pass to eth_sendRawTransaction to broadcast it. It packs the transaction fields together with the ECDSA signature (v/r/s or yParity), which is what lets this tool recover the sender.

How is the sender (from) address recovered?

The signature is verified against the transaction's signing hash to recover the public key, and the sender address is the last 20 bytes of its Keccak-256 hash. This is exactly how Ethereum nodes determine who signed a transaction, with no lookup or network call needed.

Which transaction types are supported?

Legacy (with and without EIP-155 replay protection), EIP-2930 access-list (type 0x01), EIP-1559 dynamic-fee (0x02), EIP-4844 blob (0x03) and EIP-7702 set-code (0x04) transactions. The type is detected automatically from the first byte.

Can it decode a blob transaction's blobs?

It decodes the canonical signed form of an EIP-4844 transaction: chain id, fees, blob versioned hashes and signature. It does not decode the network-wrapper form that carries the full blobs, KZG commitments and proofs, since those aren't part of the signed transaction.

Is the transaction data sent anywhere?

No. RLP decoding and secp256k1 signature recovery both run entirely in your browser via JavaScript, so nothing is uploaded and it's safe for unbroadcast or sensitive transactions.

Related tools

Keccak-256 Hash

Compute Keccak-256 hashes and Solidity function selectors online.