Ethereum Transaction Decoder

Paste a raw Ethereum transaction to see its type, Chain ID, nonce, gas, recipient, signature.

Secure (SSL)

Client-Side Processing

100% Free

Go to tool

Instructions

1

Enter data
Enter content, paste text or load a file from disk.
2

Click the button
The tool will immediately process your data in the browser.
3

Get the result
Copy the finished text or save the file to your device.

                                                function runTool() {

                                                  return "Result ready in 0.1s";

                                                }

Rate this tool:

Related tools

Other tools you may find useful

How to Use the Decoder: Paste the Raw Transaction Hex and Click Decode

The Ethereum transaction decoder lets you read the fields stored in a raw transaction. On the page you will find a text field where you enter the transaction record in hex format. After pasting the data, click the Decode button. If you do not change the example, decoding starts automatically when the page loads, so you see the result right away.

Copy the raw Ethereum transaction record from wherever you have it saved in hex form.
Paste it into the field on the page.
Click Decode and read the fields shown below.

For the default example, the result shows: transaction type legacy, Chain ID (from EIP-155) 1, nonce 9, gas price 20 Gwei, gas limit 21,000, recipient 0x3535353535353535353535353535353535353535, amount 1 ETH, data none, signature v 37, r 0x28ef61340bd939bc2195fe537567866003e1a15d3c71ff63e1590620aa636276, and s 0x67cbe9d8997f761aecb703304b3800ccf555c9f3dc64214b297fb1966a3b6d83. This shows how one string of characters can reveal the most important information about a transaction.

How to Read Transaction Fields: Nonce, Gas Price, Gas Limit, Recipient, Amount, and Data

After decoding, the result is divided into fields. Each one describes a different element of the transaction. Below is a short explanation of what the most important values mean.

Field	What it tells you
Nonce	The transaction's sequence number for a given address. It helps determine which transaction came first.
Gas price	The rate per unit of gas in Gwei. In type 0x02 transactions you will see the tip and the maximum gas price separately.
Gas limit	The maximum number of gas units the transaction can use during execution.
Recipient	An address in 0x... format, or an indication that the transaction creates a contract when the recipient field is empty.
Amount	The value transferred in the transaction, shown in ETH.
Data	Additional information attached to the transaction. The tool shows the beginning of the data, the byte count, and the selector, which is the first four bytes.
Access list	In types 0x01, 0x02, and 0x03 it shows the number of entries for addresses and storage locations the transaction can access.
Blobs	In type 0x03 you will see the maximum gas price for blobs and the number of blobs.

Ethereum Transaction Types: Legacy, EIP-155, 0x01 EIP-2930, 0x02 EIP-1559, 0x03 EIP-4844 Blob

Ethereum supports several transaction formats. The decoder recognizes them by the beginning of the record and shows the corresponding fields. This lets you check which type you are dealing with and what a given transaction contains.

Legacy — the oldest format. It contains nonce, gas price, gas limit, recipient, amount, data, and the v, r, s signature. In the EIP-155 version, the signature also contains the Chain ID, so the v field can tell you which network the transaction belongs to.
0x01 EIP-2930 — a format with a Chain ID and an access list. Otherwise it has fields similar to a legacy transaction, including a single gas price.
0x02 EIP-1559 — a format with Chain ID, tip, maximum gas price, gas limit, recipient, amount, data, access list, and signature.
0x03 EIP-4844 blob — an extension of type 0x02. In addition to the same fields, it contains the maximum gas price for blobs and a list of blob hashes. In total it has fourteen fields.

Chain ID, v/yParity, and the r, s Signature: What They Mean

Chain ID tells you which Ethereum network the transaction belongs to. This is important because the same format applies to testnets and the mainnet. In legacy transactions with EIP-155, when v is at least 35, Chain ID is calculated as (v − 35) ÷ 2. For example, v 37 gives Chain ID 1.

v in legacy — a number related to the signature and often also to the Chain ID. With v below 35, the transaction does not contain EIP-155 network information.
yParity in newer types — takes the value 0 or 1. It indicates one of the pieces of information needed to verify the signature.
r and s — two signature values. They show that the transaction was signed with a private key. The decoder displays them in full hex.

The tool does not recover the sender's address from the signature. It only shows the v, yParity, r, and s values and the other fields stored in the transaction.

Tool Limitations: No Sender Recovery, No Hash, and No Support for the Latest Types (e.g., EIP-7702)

The decoder has a few practical limitations. The most important one is that it works on the raw transaction record and does not connect to the Ethereum network. So it will not check whether the transaction was sent, confirmed, or what its current status is.

No sender recovery — the address that sent the transaction is not calculated from the signature. You will only see the signature fields.
No transaction hash — the tool does not calculate the transaction identifier. If you need the hash, you must get it from another source.
Supported types — available formats are legacy, 0x01 EIP-2930, 0x02 EIP-1559, and 0x03 EIP-4844. The latest types, such as EIP-7702, are not supported.
Data scope — the tool reads only what is in the record you provide. It does not show balances or other information outside the pasted record.

If you have a transaction in a format other than raw hex, first obtain its raw record. Only that string of characters can be pasted into the decoder.

Frequently Asked Questions

What is an Ethereum transaction decoder?

It is a tool that turns a raw Ethereum transaction record in hex format into readable fields. It shows, among other things, the transaction type, Chain ID, nonce, gas price, gas limit, recipient, amount, and data. All work happens in your browser.

How do I read a raw Ethereum transaction?

Copy the transaction's hex record and paste it into the field on the page. Click Decode, and the result appears below. You can also leave the default example to see it work right away.

What does nonce mean in an Ethereum transaction?

Nonce is a number that defines the order of transactions from a given address. This keeps transactions from being processed in a random order. In the decoder you will see the nonce value read from the record.

What do v, r, and s mean in an Ethereum transaction?

v or yParity indicates information needed to verify the signature, and r and s are the signature values. In legacy transactions, v can also let you calculate the EIP-155 Chain ID. The decoder shows these values in full hex.

How does a legacy transaction differ from EIP-1559?

A legacy transaction has a single gas price, while EIP-1559 splits it into a tip and a maximum gas price. EIP-1559 also includes a Chain ID and an access list, while legacy relies on the v field. The decoder recognizes both formats and shows their fields.

Will the decoder show the sender or transaction hash?

No. The tool does not recover the sender from the signature and does not calculate the transaction hash. It only shows the fields stored in the raw transaction you paste.

Decoding happens entirely locally in your browser and is for information only — the tool does not verify the signature or confirm the transaction's validity on the network, and for unusual transaction types you should check the result in a block explorer.