BLIX
0% trading fees on every trade · every account, no code ›

AI-powered memecoin terminal

How to read a Solana transaction

A Solana transaction looks like a wall of addresses until you know the four places to look. This guide shows how to find a transaction from a signature or a wallet, what each part of it means, and the one habit that makes any swap readable in ten seconds: ignore the instructions at first and read the balance changes.

The BLIX memecoin trading terminalExplore the BLIX terminal ↗

By BLIX · Updated · Solana fundamentals and on-chain data

On this page
  1. Finding the transaction
  2. The parts of a transaction
  3. Read the balance changes first
  4. Six things that mislead
  5. When you do need the instructions
  6. Landed, confirmed, finalized
  7. Reading many transactions at once
  8. More on Solana and on-chain data

Finding the transaction

  1. From a signature. A signature is a long base58 string, usually 87 or 88 characters. It is the transaction's ID. Paste it into the search box of any Solana explorer.
  2. From a wallet. Search the wallet address instead and open its transaction list, newest first. Token transfers and swaps are often on separate tabs.
  3. From a token. Search the token's mint address (the "contract address") and open its transfers or trades. A wallet address and a mint address look alike; this guide tells them apart.
  4. From code. getSignaturesForAddress lists signatures for any address, and getTransaction returns one in full.
curl https://api.mainnet-beta.solana.com -H 'content-type: application/json' -d '{
  "jsonrpc": "2.0", "id": 1, "method": "getTransaction",
  "params": ["<signature>", {"encoding": "jsonParsed", "maxSupportedTransactionVersion": 0}]
}'

The parts of a transaction

PartWhat it isWhy you care
SignatureThe first signer's signature; the transaction's IDHow you find it again
Slot and block timeWhich block it landed in, and whenOrder matters: two trades in the same slot happened together
ResultSuccess, or an errorA failed transaction still paid its fee and did nothing else
Fee payerThe first account; pays the feeNot always the person trading: some apps pay fees for their users
SignersAccounts that authorized itWhoever signed agreed to everything in it
FeeBase fee plus priority fee, in lamports5,000 lamports per signature, plus whatever was bid for priority
Account listEvery account the transaction may touchSolana needs the full list up front; it is why transactions can run in parallel
InstructionsThe calls to programs, in orderWhat was asked for
Inner instructionsCalls those programs made to other programsWhere the real token movements usually are
LogsLines printed by the programs as they ranError reasons, and program events
Balance changesSOL and token balances before and after, per accountWhat actually happened
Compute unitsHow much work it usedPriority fee is priced per compute unit

The field names in the JSON are meta.fee, meta.err, meta.logMessages, meta.innerInstructions, meta.preBalances / postBalances and meta.preTokenBalances / postTokenBalances. The reference is Solana's transactions documentation.

Read the balance changes first

A single swap through a router can contain fifteen instructions across four programs. You do not need to follow them. Every account's balance is recorded before and after, so the net effect is a subtraction.

A worked example with made-up round numbers. A wallet's rows in one transaction:

AccountBeforeAfterChange
Wallet, SOL2.5000000001.993406560−0.506593440
Wallet, token X03,412,000+3,412,000

The wallet bought 3,412,000 of token X. But it did not pay 0.5066 SOL for them. Three other things came out of that SOL:

Where the SOL wentAmountHow you can tell
The swap itself0.500000000The pool's or curve's SOL balance rose by this
Network fee0.000105000meta.fee: 5,000 lamports base plus a 100,000 lamport priority fee
Rent for a new token account0.001488440A new account for token X appears in the list, holding this much SOL
A tip0.005000000A plain SOL transfer to an address that is not the pool

So the price paid was 0.5 SOL for 3,412,000 tokens, and the all-in cost was about 0.5066. Getting this wrong by using the wallet's total SOL change as the trade size is the most common error in home-made profit trackers. The rent comes back if the token account is closed later; the fee and the tip do not.

Six things that mislead

  • Wrapped SOL. Many pools trade wrapped SOL, a token that represents SOL. A swap can create a wrapped SOL account, use it and close it inside one transaction, so SOL seems to move twice. Net the wallet's SOL and it reads correctly.
  • Routed swaps. A router may go SOL to token A to token B. The middle token appears and disappears. Only the first and last legs are the trade.
  • Fee payer is not the trader. When an app pays network fees for its users, the first account is the app. The trader is whoever's token balance changed.
  • Failed transactions. They appear in a wallet's history and cost a fee. Check the result before reading anything else.
  • Unrequested transfers. Anyone can send any token to any wallet. A tiny transfer from a lookalike address, or a token named like a website, is bait, not something the wallet did.
  • Versioned transactions. Modern transactions can load extra accounts from address lookup tables. If account numbers in an instruction seem to point past the end of the list, the rest are in meta.loadedAddresses.

When you do need the instructions

Read them when the balances cannot answer the question: which program was used, what limit was set, why it failed. Each instruction names a program and the accounts it was given. Explorers decode the common programs into words (transfer, swap, create account). For an unknown program you get raw bytes, and the logs are usually the fastest way to see what it did. On a failure, the last few log lines name the program that returned the error and usually a readable reason, such as a slippage limit being exceeded.

Landed, confirmed, finalized

A transaction is processed when a node has seen it in a block, confirmed when two thirds of stake has voted on that block, and finalized about thirteen seconds later. Explorers default to confirmed or finalized, so a transaction can be real and not yet searchable for a moment. If a signature never appears, it was never included: the blockhash it was built on expired, which happens after about 150 blocks, and nothing was charged.

Reading many transactions at once

Reading one transaction by hand teaches you the format. Reading a wallet's last five hundred to work out its record is a job for software. BLIX does that reading for every Solana wallet: a wallet page shows each swap already netted into what was bought, what was sold and for how much, with realized and open results kept apart. The wallet tracking guide covers how to read that view, and on-chain analytics explained covers how such views are built.

More on Solana and on-chain data

This page is education about how the technology works. It is not financial advice, and nothing here recommends buying or selling anything.

Frequently asked questions

How do I look up a Solana transaction?

Paste its signature (the long ID your wallet shows after sending) into a Solana explorer's search box. Without the signature, search the wallet address and find it in the transaction list.

What is a Solana transaction signature?

The cryptographic signature of the transaction's first signer. It is unique, so it doubles as the transaction's ID, sometimes called the transaction hash.

Why did my failed Solana transaction cost a fee?

Validators did the work of processing it, so the network fee is charged whether it succeeds or not. Nothing else in the transaction takes effect.

How do I see what a wallet paid in a swap?

Compare the wallet's SOL and token balances before and after, then subtract the network fee, any rent for a new token account and any tip. What is left is the trade.

What does fee payer mean on Solana?

The account that pays the network fee, always the first signer. It is usually the user, but apps can pay fees on behalf of their users, so it does not always identify who traded.

Your next move starts here.

Create your BLIX account to access the trading terminal. Join the Discord community to stay connected.