Read Solana wire structure without chain lookups
A serialized transaction contains signatures and a compiled message. The message records a header, static account keys, a recent blockhash, compact instruction account indexes, and—on v0 transactions—address lookup table metadata. This decoder preserves those facts without inventing unavailable lookup-table addresses.
How to decode a serialized Solana transaction
- Choose the exact encoding used by the serialized bytes: Base64, Base58, or hexadecimal.
- Paste the full transaction or load a deterministic legacy or v0 fixture, then decode locally.
- Review signer state, static account roles, program indexes, raw instruction data, and unresolved lookup metadata before using independent chain context.
Decoding is not simulation or a safety verdict
This tool does not fetch a transaction from a signature, resolve address lookup table contents, inspect program code, simulate execution, predict balance changes, sign, or broadcast. A structurally valid transaction can still be malicious, stale, incomplete, or inappropriate for your intended action.
Related Solana and Web3 tools
Frequently asked questions
- Can I paste a transaction signature?
- No. A signature is an identifier or signature value, not the serialized transaction bytes. This offline decoder never queries RPC endpoints.
- What is different about a v0 transaction?
- A v0 message can reference address lookup tables. The serialized transaction includes table addresses and indexes, but not the account addresses stored in those tables.
- Does a successful decode prove a transaction is safe?
- No. It only proves that the bytes fit the supported wire format and exposes deterministic fields available in those bytes.
- Why are some programs not named?
- The decoder labels only reviewed well-known program IDs available as static account keys. Lookup-resolved or unrecognized programs remain explicitly unknown.