TALENTRE

Research

Solana explorer guide: follow the tokens behind a swap

Archival card drawer with a TX index tab beside the title Solana Explorer

One Solana swap can show several transfers, unfamiliar addresses and a SOL debit larger than the order. Adding every transfer together gives the wrong trade size. Use the transaction signature to identify the accounts involved, then reconcile what actually entered and left your wallet.

In this article

Start with the signature, not the ticker

Open the transaction from your wallet's history, or paste its signature into a Solana explorer. Confirm the network, time and execution status. A wallet address opens an account's activity; the signature opens one specific transaction. For a completed trade record, also check the confirmation level.

The search result determines what you are reading:

IdentifierWhat it identifies
Transaction signatureOne submitted transaction, which can contain several instructions.
Wallet addressThe account whose activity or balances you want to inspect.
Token mintThe exact token, regardless of its name or ticker.
Token accountA balance for one mint under a particular token owner.
Program addressExecutable code handling an operation, such as a swap or transfer.

Copy the full mint from the transaction before opening another chart. A matching ticker is not enough to identify the same asset.

Separate the fee payer, token owner and recipient

The fee payer funds the network charge. The transfer authority authorizes a movement. The destination receives it. These roles can belong to different addresses, so the first signer is not automatically the buyer or seller.

For a token transfer, inspect the source and destination token accounts. Read each account's mint and token-owner field. The destination token-account address may differ from the wallet address you expected because tokens are held in separate accounts.

Watch the two meanings of owner. An account's program owner controls its data; for a token account, that is a Token Program. The owner inside the token-account data is the authority over its tokens. Treating the program owner as a trader can make thousands of unrelated transfers appear connected.

Follow the swap through its inner instructions

Expand the instruction details. Top-level instructions are the operations submitted in the transaction. Inner instructions record calls that a program made to another program while executing. A swap program can call the Token Program to move the input and output assets.

An aggregator route can pass through multiple pools or intermediate tokens. Those movements explain execution; they are not separate buys by your wallet. Follow source and destination accounts until the route returns the output to an account owned by your wallet.

Also identify account creation, SOL wrapping and account closure. These operations help explain balance changes that a simplified swap label leaves out. An undecoded instruction needs program-specific interpretation; a familiar program name alone does not establish the amount received.

Measure token amounts from before-and-after balances

Use the token balance changes to reconcile the instruction view. In raw transaction data, the relevant lists are preTokenBalances and postTokenBalances.

  1. Match each token account using its account index and mint. Resolve the complete account list, including addresses loaded through lookup tables.
  2. Confirm its token owner so pool reserves and intermediary accounts stay outside your wallet's total.
  3. Subtract before from after using the integer amounts, then apply the mint's decimals.
  4. Combine accounts for the same wallet and mint to obtain the net change. Transfers between those accounts should cancel out.

A newly created account may have no before entry; a closed account may have no after entry. Treat the missing side as zero only after confirming that lifecycle in the instructions. Missing metadata alone is not a zero balance.

This reconciliation gives the quantity the wallet gained or lost. An explorer's dollar estimate is a separate valuation and can differ from the value at execution.

Explain the SOL difference before calling it a fee

The wallet's SOL change can include swap funding, the network fee, account-storage deposits and returned balances. Read the recorded transaction fee separately. Account creation can leave SOL in a token account as its minimum storage balance; that amount is not a trading fee.

When an account closes, its lamports go to the destination specified in the closing instruction. Check that destination rather than assuming the original account funder received the refund.

Wrapped SOL adds another accounting step. SOL deposited into a WSOL account becomes a token balance when synchronized. Closing that account releases its remaining SOL. Wrapping and unwrapping can therefore appear beside a swap without representing another purchase or sale.

Reconcile the wallet's SOL and WSOL together, counting the same funds once. Keep storage deposits and refunds separate from the trade amount. A smaller SOL debit after an account closure does not mean the swap received a better price.

Keep a record that identifies the actual trade

Save the signature, network, confirmation level, full input and output mints, net token changes and network fee. Add any account deposit or refund that explains the SOL difference. This record lets you compare the completed trade with the quote you accepted.

To inspect where that token trades now, paste the verified mint into Talentre's Solana pool comparison. It compares returned token/WSOL markets; the transaction remains the record of your historical execution.

For an unsuccessful execution, follow the Solana transaction failure guide before interpreting attempted transfer instructions as completed movements.

Frequently asked questions

How do I find my Solana transaction signature?

Open the transaction in your wallet's history and select its explorer link. Copy the signature from the transaction page. Searching a wallet address instead shows activity across transactions.

Is a token account the same as a wallet address?

No. A token account holds one mint for a token owner. A wallet can control multiple token accounts, including more than one for the same mint.

Does the fee payer own the tokens being transferred?

Not necessarily. Fees can be sponsored by another account. Inspect the source token account and transfer authority before identifying who authorized the movement.

Why does one swap show several token transfers?

A route can use multiple pools and intermediate assets. Inner instructions expose these movements. Reconcile the wallet's balances by mint to determine its net input and output.

Why did my SOL balance fall by more than my swap amount?

The transaction can also pay network fees, fund account storage or leave SOL wrapped. Read the fee, account-creation instructions and remaining WSOL balance to explain the difference.

Does closing a WSOL account mean the tokens were sold?

Closing a WSOL account releases the underlying SOL to a specified destination. It is an unwrap operation. Check the other instructions to see whether a swap also occurred.

Questions or corrections? Contact the Talentre team.

← All articles