Official site — always check you are on kripicard.comVerify
Web3 tools
Transaction Decoder
Paste a raw signed transaction to read its envelope: type, chain, nonce, gas, value and the address recovered from the signature. Everything is computed from the payload itself, so unbroadcast transactions decode too.
This is the full signed payload broadcast to the network — not the transaction hash, and not the calldata on its own. It decodes offline, so an unbroadcast transaction works too.
Transaction types
The first byte of a modern transaction identifies its envelope format. Legacy transactions have no type byte at all and begin directly with RLP.
| Type | Name | Fee fields |
|---|---|---|
| — | Legacy | gasPrice |
| 0x01 | EIP-2930 | gasPrice, plus an access list |
| 0x02 | EIP-1559 | maxFeePerGas, maxPriorityFeePerGas |
| 0x03 | EIP-4844 blob | Adds maxFeePerBlobGas |
| 0x04 | EIP-7702 | Adds an authorization list |
The fee shown as maximum cost is gas limit multiplied by the maximum fee. Real transactions almost always cost less, because the base fee is usually below the cap and unused gas is never charged.
Related tools
- ABI Decoder — decode the input data on its own, with or without an ABI.
- Gas Fee Estimator — what those fee fields would cost right now across 50 chains.
- Wallet Address Checker — verify the recovered sender or destination address.
Frequently asked questions
What is a raw transaction?
It is the complete signed payload broadcast to the network: the envelope fields plus the ECDSA signature, RLP-encoded into one hex string. It is not the transaction hash, and it is not the calldata on its own.
How is the sender recovered without a node?
The signature is over the transaction contents, so the public key and therefore the address can be recovered mathematically. Nothing is looked up. If a field were altered the recovered address would change, which is what makes tampering detectable.
What do the transaction types mean?
Type 0 is the original legacy format. Type 1 adds an access list. Type 2 is the EIP-1559 fee market with a max fee and priority fee. Type 3 carries blobs for rollup data, and type 4 is EIP-7702 account delegation.
Can I decode a transaction I have not broadcast yet?
Yes, and that is the main reason to use this. Decoding is pure maths on the payload, so a transaction prepared offline can be inspected before it is ever sent.
How is this different from an ABI decoder?
An ABI decoder reads the input data of a call. This reads the whole signed envelope around it: who signed, on which chain, with what nonce and fee. If the transaction carries a recognised call, the input is decoded too.