Read a transaction before you sign it

Paste a serialized Solana transaction and Evidesa decodes it: which programs it calls, what each instruction does where the program's layout is published, which accounts it can modify, and which of them it could not resolve.

This is a decode, not a verdict. It cannot tell you whether a transaction is worth signing — it can only tell you what the bytes say, so that you are deciding against the transaction itself rather than against the description someone gave you of it.

WholeWhat the instrument does to any transaction: the envelope opened into its instruction lanes — 5 drawn here — each checked against the published-layout registry.Drawn3 lanes carry the registry's scribe marks: their programs publish a layout the decoder can name, instruction by instruction.Not drawn2 lanes are plain stock — their programs are not in the registry, so the bytes stay undecoded. Plain, not hatched, because an unrecognised program is not thereby suspicious. Nothing is simulated, and no real transaction is drawn here.

Serialized transaction

Instructions, in execution order
#	Program	Decoded as	Account writes
No transaction decoded

The full serialized transaction, as base64 or base58 — not a signature, not an account address, and not a transaction message on its own.

What this cannot do. Most Solana programs are not in the decoder's registry and cannot be: naming a program from a transcribed address risks attaching a familiar name to the wrong one, which is worse than leaving it unnamed. Only the native programs and the token programs, whose addresses and layouts come from the Solana SDK itself, are named here. An unrecognised program is not thereby suspicious, and a recognised one is not thereby safe.

Address lookup tables. A version-0 transaction can reference accounts stored in on-chain tables rather than carrying them. Those tables are read from the Solana RPC provider this app uses, which tells that provider which tables were looked up. When a table cannot be read, the accounts it would have supplied are reported as unresolved rather than guessed at.

What happens to what you paste. It is decoded in memory and the result is returned to your browser. It is not stored, not written to any log, not sent to analytics, and never placed in a URL. Text carried inside the transaction — a memo, for example — is reported by length and not displayed, because it is written by whoever built the transaction and would otherwise be able to make claims in this page's voice.

Evidesa is not financial advice and does not certify safety.