Decoded Transaction
Pronunciation: dee-KOH-did tran-ZAK-shun
Definition
A decoded transaction is a raw blockchain transaction translated from protocol encoding into readable fields such as sender, recipient, amount, fee, contract function, accounts, and instructions. Decoding improves analysis and user review, but it is an interpretation, not proof of execution or intent. Accuracy depends on the correct network rules, transaction version, ABI or program schema, token metadata, and decoder.
Overview
Meaning and scope
A decoded transaction is a raw blockchain transaction translated from protocol encoding into readable fields such as sender, recipient, amount, fee, contract function, accounts, and instructions. Decoding improves analysis and user review, but it is an interpretation, not proof of execution or intent. Accuracy depends on the correct network rules, transaction version, ABI or program schema, token metadata, and decoder.
Mechanism and operation
Blockchain transactions are transmitted as structured binary or hexadecimal data. A decoder parses the envelope, signature fields, account references, values, and call data according to the target protocol. For contract interactions, it may use an ABI, instruction definition, or known program layout to display function names and parameters. A wallet can decode a transaction before signing, a node can expose decoded fields through an API, and an indexer can decode executed logs or instructions after inclusion. A pre-signing display describes requested actions, while receipts, internal calls, and post-state describe what actually occurred. Incorrect token decimals, spoofed symbols, unverified ABIs, proxy implementations, or outdated program schemas can make a dangerous transaction look harmless.
Practical payment example
An explorer labels a transaction as a token transfer after decoding contract inputs, but finance also checks the emitted event and receipt.
Operational checks
Secure interfaces should show the network, raw destination, asset contract, integer amount, permissions, and unknown data. They should not replace an address with a friendly name unless the mapping is authenticated. Simulation can add context, but simulation results are also conditional on state and provider behavior.
Distinctions and limits
Without the correct schema, a decoder can identify bytes but not reliably explain their business meaning. A Contract Transaction may produce effects that are not obvious from the top-level input.
Related reading
Related definitions: transaction, Contract Transaction.
Example
An explorer labels a transaction as a token transfer after decoding contract inputs, but finance also checks the emitted event and receipt.
Comparison
Without the correct schema, a decoder can identify bytes but not reliably explain their business meaning. A Contract Transaction may produce effects that are not obvious from the top-level input. They should not replace an address with a friendly name unless the mapping is authenticated.
Key Takeaway
A decoded transaction makes protocol data readable, but only raw data, verified schemas, execution evidence, and finality establish what truly happened.
Sources
- Ethereum JSON-RPC API — Ethereum Foundation (2026-08-02)
- Ethereum Transactions — Ethereum Foundation (2026-08-02)
- Solana Transactions — Solana Foundation (2026-08-02)