A wallet's activity feed is a summary, not a source of truth. When a swap settles differently than you expected, or the transaction disappears after you signed, the on-chain record is the authoritative one. That record is public and permanent. A block explorer reads it directly from the validator history, with no app layer in between.
This post walks through every section of a Solana transaction page so you can interpret what actually executed, not just what an interface told you.
Grabbing the Transaction Signature
The signature is the primary key for any Solana transaction: a base58-encoded string that uniquely identifies the write to the ledger. You can get it from three places:
- Wallet activity. Phantom, Solflare, and Backpack each let you tap a past transaction and open it directly on an explorer.
- The swap interface. Most apps surface a "view transaction" link immediately after confirmation.
- Your wallet address. Drop your public key into the search bar on any explorer and you get the full transaction list, newest first.
Solscan, Solana Explorer, and SolanaFM all index the same chain. The underlying data is identical; the presentation differs.
Status, Timestamp, and Network Fee
The overview section at the top resolves three things immediately.
Status. A "Success" result means the transaction was committed to the ledger and every instruction ran. A "Failed" result means none of them did. Solana transactions are atomic: a failed swap cannot leave you partially through a route. Either everything executes or nothing does.
Timestamp and block. This tells you when the transaction was finalized. If a swap appears to have vanished, a missing signature almost always means the transaction expired before any validator picked it up, not that it failed mid-flight. No signature means no state change.
Fee. Denominated in SOL, this is the base fee plus any priority fee the app attached to improve landing probability. Even a failed transaction pays this fee, because validators had to process it to determine it failed.
The Token Balance Change Table
This is the section to focus on for any swap analysis. Solscan labels it "Token Changes" or similar. Solana Explorer lists it under token balances before and after.
It shows the exact net movement of every token involved in the transaction for your account. That means the final received amount after all pool fees and any price impact during execution. Compare that number to the minimum received figure you saw in the confirmation UI before signing. A successful swap can return less than the quoted estimate, but it cannot return less than your slippage-adjusted minimum.
You may also see a small SOL deduction beyond the fee. That is typically rent: roughly 0.002 SOL allocated when the swap opens a new SPL token account for a token your wallet did not previously hold. That SOL is not lost; you can reclaim it later by closing the empty account.
Reading the Instruction Trace
A Solana swap transaction is composed of instructions, each calling a specific on-chain program. Explorers identify programs by name where possible, so you will see the routing program followed by individual AMM pool programs like Raydium, Orca, or Meteora.
Each pool hop appears as an inner instruction, with a token transfer in and a corresponding token transfer out. Read the stack top to bottom and you can reconstruct the full route: SOL into pool A, USDC out, USDC into pool B, target token out. A multi-hop route produces a longer instruction trace but is still one atomic transaction.
Wrapped SOL (WSOL) appearing in the instruction log is expected behavior. SPL-based pools require the wrapped form of native SOL, and the routing program typically wraps and then unwraps within the same transaction.
Diagnosing a Failed Transaction
When Status reads Failed, the program logs at the bottom of the page tell you which instruction stopped execution and why. The final lines are the most informative. Common patterns:
- Slippage or minimum-output violation. The on-chain price at execution time fell outside your tolerance, so the program halted rather than fill at the worse rate.
- Insufficient balance. Either the input token amount was short, or there was not enough SOL left to cover fees and account rent.
- Compute budget exceeded. The route consumed more compute units than the transaction requested. Retrying with a less complex route often resolves this.
Some programs emit a human-readable string; others return a numeric error code. The program name adjacent to the error identifies which step in the route broke down.
What the Explorer Does Not Expose
An explorer shows committed on-chain state. It has no record of the quote your app displayed before you signed, and it cannot modify or reverse any transaction. A confirmed swap is final. Treat these pages as read-only audit logs, and avoid any site that claims it can recover or reverse a swap by connecting your wallet to an explorer-adjacent interface.
Verifying the Route Before It Executes
swap.io, a Solana swap aggregator that compares quotes from multiple routing providers (Jupiter among them), surfaces the full route, price impact, and minimum received amount before you sign. Reviewing that screen before confirming is the on-ramp to understanding what an explorer will show you afterward.
Key Takeaways
- The transaction signature is the unique identifier for every on-chain lookup.
- Failed transactions are atomic: no partial fills, no mid-route state.
- The token balance change table shows what your wallet actually received, net of all fees and price impact.
- The instruction trace maps the route pool by pool.
- Program logs at the bottom of a failed transaction identify which step stopped execution and why.
Frequently Asked Questions
Is sharing a transaction signature a security risk?
No. The transaction is already public on-chain. Sharing the signature only lets someone view a record that anyone can already find. Your seed phrase and private key are the credentials that must stay private.
Why does my swap have no signature and nothing on the explorer?
The transaction likely expired before it landed in a block. No signature means no state change occurred, and your token balances were not affected. Retry the swap.
Why does the explorer show a different received amount than my wallet app?
Wallet apps often round figures or exclude small dust amounts. The explorer reports exact on-chain values, including every fee and rent deduction to the lamport.
Can I look up transactions for a wallet address I do not own?
Yes. All Solana wallet history is public by design. If you know an address, you can inspect every transaction it has ever signed, which is worth keeping in mind any time you share your own address.
Top comments (0)