Web3 Lab · T.09
Transaction Decoder
Paste raw hex — read type, nonce, gas, recipient, value and signature. Legacy, type 1, type 2.
This decoder needs JavaScript (runs locally in your browser).
Note: only structure and values are decoded — no signature check against an address (for that: Address Validator and Message Verifier). Recipient addresses can be checked with one click.
What a transaction contains
Every Ethereum transaction is an RLP-encoded list — byte by byte, no field names. The type is in the very first byte: 0xc0… means legacy, 0x01 type 1, 0x02 type 2.
| Field | Meaning |
|---|---|
| Nonce | Sender transaction counter — gaps block all following transactions |
| Gas price / max fees | Legacy: one price. Type 2: bid (priority) + cap (max fee) per gas unit |
| to | Recipient — empty means contract creation |
| v, r, s | The signature (r, s) plus parity/chain protection (v) |
Go deeper: What is a nonce? · Why Ether has 18 decimals
Frequently asked questions
What does the decoder show?
Type, signature status, chain ID, nonce, gas price or max fees, gas limit, recipient, value, data, access list and v/r/s — including maximum total cost.
Where do I get raw hex?
From wallets in expert mode, from block explorers or your own software. To try it: sample buttons above.
What is the difference between type 0, 1 and 2?
Type 0 (legacy) uses a single gas price. Type 1 (EIP-2930) adds an access list. Type 2 (EIP-1559) uses max priority fee and max fee — today's standard.
Does my transaction leave the browser?
No — purely local RLP decoding. Note: raw hex contains no private keys, but sensitive data still does not belong on other people's computers.
Planning transactions, payments, agent money flows?
From gas models to custody concepts to agent payments (x402) — I help you assess and build.