Guide

How to read a Solana transaction on Solscan

Every SOL transfer on Solana leaves a public record. Solscan is the most widely used block explorer for reading those records — whether you just paid for a game roll, sent SOL to a friend, or received a deposit from an exchange. This guide walks through a typical transaction page field by field so you know exactly what you are looking at.

What is a block explorer?

A block explorer is a search engine for a blockchain. Solana processes thousands of transactions per second; explorers like Solscan, Solana FM, and the official Solana Explorer index that activity and present it in a human-readable format. You do not need an account to use them — paste a wallet address or transaction signature and the site fetches the on-chain data.

Solscan is popular because it loads quickly, labels known programs (Jupiter, Raydium, etc.), and shows token transfers in plain language. The concepts below apply to other explorers too; field names may differ slightly.

Two ways to open a transaction

From your wallet

After you approve a transfer in Phantom, Solflare, or Backpack, the wallet shows a confirmation with a transaction signature — an 87-character base58 string. Tap it to copy, then paste into Solscan's search bar at the top of solscan.io. The URL will look like solscan.io/tx/<signature>.

From a wallet address

Search your own wallet address on Solscan to see recent activity. Click any row in the transaction list to open the full detail page. This is useful when you forgot to copy the signature but know roughly when you paid.

Prefer an inline check without leaving this site? Use our verify Solana payment guide — it includes a live transaction lookup tool.

The overview panel — read this first

At the top of every Solscan transaction page you will see a summary strip. Focus on these fields:

  • Result / Status — should say Success or Finalized. If it says Failed, no SOL moved (aside from the fee in some cases). Do not treat a failed tx as payment.
  • Timestamp — when the block was produced. Compare to when you tapped Approve in your wallet; they should be seconds apart on mainnet.
  • Signature — the unique ID of this transaction. Share it with support or paste it into payment-detection forms on dApps.
  • Slot — the Solana block height. Useful for developers; casual users can ignore it.
  • Fee — network cost in SOL (typically 0.000005 SOL for a simple transfer). This is separate from the amount you sent.

A successful simple SOL transfer usually confirms in under a second. If Solscan still shows "Processing" for more than a minute, the RPC may be lagging — refresh or try the official Solana Explorer as a cross-check.

Understanding the balance changes

Scroll to the SOL Balance Change or Token Balances section. For a plain SOL payment you will see two addresses with opposing numbers:

  • Sender (your wallet) — negative change equal to amount sent plus fee. If you sent 0.001 SOL, you might see roughly −0.001005 SOL.
  • Receiver (merchant or friend) — positive change equal to the payment amount only (0.001 SOL in that example). They do not pay your network fee.

Always verify the receiver address matches who you intended to pay. Phishing sites sometimes show the correct amount but a different destination. Compare the full address character by character, or at least the first and last six characters.

Token swaps and NFT mints look more complex — multiple programs appear in the instruction list. For micropayments to a game or shop, you usually only need the simple two-party SOL transfer described above.

Instructions and programs (when to care)

Below the balance table, Solscan lists Instructions — the low-level steps the transaction executed. A basic wallet-to-wallet SOL send typically shows:

  1. System Program: transfer — moves lamports from one account to another.
  2. Optionally Compute Budget instructions if your wallet added a priority fee.

You do not need to decode raw instruction data for everyday payments. The balance-change table is enough. Developers and auditors use the instruction view to debug failed swaps or smart-contract calls.

If you see unfamiliar program names after clicking a link in a spam token notification, stop — that is a common phishing pattern. See our Solana spam tokens guide for how to hide scam airdrops safely.

Fees: base fee vs priority fee

Solana charges a fixed base fee per signature — 5,000 lamports, or 0.000005 SOL. During network congestion, wallets may add an optional priority fee so validators process your transaction sooner. The total fee line on Solscan is the sum of both.

Fees are tiny compared to most payments. A 0.001 SOL Garden Dice roll might cost 0.001005 SOL all-in. For a deeper breakdown, read Solana transaction fees explained.

Mainnet vs devnet — check the cluster

Solscan defaults to mainnet. Devnet and testnet are separate networks with worthless SOL used only for development. A transaction that succeeded on devnet does not pay a live merchant.

If your wallet was on Devnet but the site expects mainnet, Solscan will show a successful transfer that the merchant never sees. Switch your wallet to Mainnet Beta and retry — our wrong network guide covers Phantom, Solflare, and Backpack.

On Solscan, confirm the cluster selector (usually top-right) says Mainnet before you interpret any balance.

Common Solscan readings and what they mean

Success — amount matches, receiver correct

Payment is done. Return to the site you paid (game, shop, tip jar) and submit the signature if it asks for manual confirmation. Garden Dice also auto-detects recent payments to its treasury when you tap "I've paid — detect and roll."

Success — but amount is wrong

You sent SOL, but not the price the merchant expected. Underpayment often happens when users round down or confuse USD with SOL. Send the difference in a second transaction or contact support with the signature.

Failed

No transfer occurred. Typical causes: cancelled in wallet, insufficient spendable SOL, or a simulation error. Your balance should be unchanged except in rare fee-only failure cases. See the transaction failed hub.

Transaction not found

Wrong signature pasted, typo, or RPC delay. Wait ten seconds and search again. Also confirm you are on mainnet and not looking up a devnet signature on mainnet Solscan.

Privacy and safety on explorers

Solana addresses and transactions are public by design. Anyone with your wallet address can see your balance history on Solscan. That is normal — it does not expose your private key or seed phrase.

  • Never type your seed phrase into Solscan or any explorer — real explorers never ask for it.
  • Solscan ads and suggested tokens are not endorsements. Ignore "claim" buttons in explorer UI.
  • Bookmark solscan.io directly; fake explorer sites exist to phish signatures.

Practice: verify a real micropayment

The best way to learn Solscan is to make a small mainnet payment and read it yourself.

  1. Fund a wallet with a little mainnet SOL (see your first Solana payment).
  2. Roll Garden Dice for 0.001 SOL or use the free demo first.
  3. Copy the transaction signature from your wallet.
  4. Paste it into Solscan and confirm status, amount, and receiver.
Beat roll of 4 — 0.001 SOL Free demo first

Related guides and tools