How to read a Solana transaction
November 15, 2026 · 5 min read · by the Rugsight team
A Solana transaction is a signed list of instructions plus the account changes those instructions produced. Explorers show both. The useful reading order is not "start at instruction 0 and go down." It is: confirm the signature, read the status and the fee, identify the fee payer, then look at net balance changes for the wallets you care about, and only then use the instruction list to name the programs that ran. This guide walks through that order with recorded mainnet transactions and a Rugsight transaction explainer that turns one signature into a short template summary.
It does not replace an explorer. It also does not score a token. For token-level checks after you know which mint moved, see how to check a Solana token for rug-pull risk. For reading a token page on Solscan, see how to read a Solana token on Solscan.
Free score in seconds. No sign-up, no wallet. Mint addresses and links from DexScreener, Jupiter, pump.fun, Birdeye, Solscan and GMGN all work.
No mint handy? Open a token our scanner just checked (free, live data):
Start with the signature, not the ticker
A transaction is identified by a signature: 64 bytes, written as a long base58 string (typically 87 or 88 characters). Wallet addresses and mint addresses are also base58, but they are 32-byte public keys and are shorter. Pasting a wallet into a transaction search will not open the transfer you meant.
You can paste a signature into Solscan at https://solscan.io/tx/<signature>, into another explorer, or into Rugsight at /tx/<signature>. Rugsight rejects strings that are not 64-byte signatures, so a mint or a wallet address will not be treated as a transaction.
Status and fee come first
Every landed transaction has a status (success or failed) and a fee in SOL, paid by the fee payer (account index 0, which must sign). The fee is charged when the transaction is processed, including when it fails. That is a separate topic, covered with a recorded example in why a failed Solana transaction still charged a fee.
A successful transfer looks ordinary once you have those three fields. On 4 November 2026 at 16:13 America/Fortaleza, signature pLfmnbRerwQbEaszxHpfmwpVNLCpCgoSWqUxMJRbwQCx2vQq29B9EnywEi9VuHT2MPtyxEPDfoUWuv27NoVg6Lg transferred 0.020989982 SOL from MYX77HJgreFrwQzXuqUXStbH54S3Bm818nsSPMQPP46 to 7Z156pFA5mf1k6hfRdwprztz3DjkXnvfMgGrD7beTqNU. The fee was 0.000005003 SOL. Status: succeeded. Rugsight's summary for that signature is a single transfer sentence plus the fee and the status. The same page is at /tx/pLfmnbRerwQbEaszxHpfmwpVNLCpCgoSWqUxMJRbwQCx2vQq29B9EnywEi9VuHT2MPtyxEPDfoUWuv27NoVg6Lg.
A token transfer is the same shape with a mint attached. On 14 November 2026 at 11:48 America/Fortaleza, signature 5nkhFMU7kgAfr8ff9D1eYoyL3BRYKFG5YBpQYd6FjqGftXLU6QExWFPRwvgC4EJZKuWLj5cHKMpL5mHAxdWrPsXH moved 1179.860135 USDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v) between two wallets, with a fee of 0.0001065 SOL. The mint, not the ticker, is what identifies the asset.
Read net balance changes before the instruction list
The instruction list is a program trace. It is easy to over-read. A Jupiter or Raydium swap can include a wrapped-SOL account being created, funded, synced, swapped and closed, plus inner transfers between pool vaults, plus a tip to a relayer. Those are real instructions. They are not each a separate "thing the user did."
Net balance changes answer the user-level question: which assets left or entered the signer's wallet, after the fee is set aside? For SOL, that is the difference between preBalances and postBalances on the signer's account, with the transaction fee added back so it is not double-counted as a transfer. For tokens, it is the difference between preTokenBalances and postTokenBalances on accounts owned by that signer.
If those nets show one asset down and one asset up, and a known swap program ran, you can honestly say the signer swapped X of A for Y of B. If they do not pair — one-sided leftovers, a second asset, or hops that only appear on pool accounts — the honest statement is to name the programs and list the nets, not to invent a route. Examples of both outcomes are in how to check what a Solana swap actually did.
Wrapped SOL (mint So11111111111111111111111111111111111111112) is native SOL in a token account. A wrap moves SOL from the wallet into that account; an unwrap moves it back. Counting the wallet's SOL change and the WSOL token change together, and not counting the native lamports sitting inside the WSOL account a second time, keeps a wrap from looking like a swap.
Programs, inner instructions, and unknown ids
Each instruction names a program id. Some programs are well known and can be labelled: the System Program, SPL Token, Token-2022, the Associated Token Account program, Compute Budget, Memo, Jupiter, Raydium, Orca Whirlpool, Meteora, pump.fun. Inner instructions are calls those programs made. They matter when you want the hop list; they are noisy when you only want the signer's net result.
An unrecognised program id should stay unrecognised. Rugsight labels it "unknown" and says it could not describe that instruction. That is not a verdict about the program. It means this explainer does not have a template for it.
Compute Budget instructions only set limits and fees. They are not transfers. Memo instructions, when present, are a short text field, not a movement of funds.
What the explainer will and will not say
Rugsight's explainer builds a template from one getTransaction result (jsonParsed). It can describe SOL transfers, SPL Token and Token-2022 transfers (including a withheld transfer fee when that is visible), approvals, revokes, account creation and closures, and the swap sentence above when the nets pair. Failed transactions include a one-line meaning of meta.err when we have one, and they still show the fee. Unknown programs stay unknown. It does not simulate a transaction, suggest a fix, or call an LLM.
Paste a signature on /tx, or open /tx/<signature> directly. The result page is not indexed. The explanation is automated technical data from public on-chain sources, not a safety guarantee and not financial advice.
FAQ
How do I open a Solana transaction if I only have the signature?
Paste the full signature (the long base58 string, typically 87 or 88 characters) into an explorer at https://solscan.io/tx/<signature>, or into Rugsight at /tx/<signature>. Do not paste a wallet or a mint; those are different kinds of address.
Why does a Solana transaction list so many instructions for a simple swap?
Aggregators and AMMs often create or close temporary token accounts, wrap or unwrap SOL, hop through pool vaults, and pay a small tip. Those inner transfers are part of the program trace. The signer's net balance changes are the clearer summary of what the wallet received and spent.
What is the difference between the fee payer and the signer on a Solana transaction?
The fee payer is account index 0 and must sign. Many transactions have only that signer. Some have a second signer: a relayer pays the fee, and the user signs because their tokens move. When you read nets, look at the wallet that owns the token accounts, not only at whichever account paid the fee.
Can Rugsight explain a transaction that is still landing?
If the signature is valid but the RPC has not yet produced a getTransaction result, the explainer reports that the transaction was not found. It may still be landing, or the signature may be wrong. Wait and retry; the explainer does not invent a result from the mempool.