How to check what a Solana swap actually did
November 15, 2026 · 5 min read · by the Rugsight team
A Solana swap is often a long program trace: an aggregator, one or more pools, a wrapped-SOL account, inner transfers between vaults, and sometimes a tip. The question most people have is shorter: what left my wallet, and what entered it? That question is answered by the signer's net balance changes, not by counting every inner transfer. This guide shows how to read those nets, when a one-sentence summary is honest, and when it is not, using recorded mainnet transactions from 15 November 2026.
The reading order for any transaction is in how to read a Solana transaction. You can paste a signature into Rugsight at /tx. After you know which mint you received, the token-level checklist is how to check a Solana token for rug-pull risk.
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):
Look at the signer's nets, not every hop
For the wallet you care about:
- Take native SOL before and after, then add back the transaction fee so the fee is not treated as part of the swap amount.
- Add any wrapped-SOL token change (mint
So11111111111111111111111111111111111111112) to that SOL figure. A wrap or unwrap is the same asset moving between the wallet and a token account. The native lamports inside the WSOL account are that same SOL and should not be counted twice. - Sum token changes by mint for accounts owned by that wallet, not for every token account in the transaction. Pool vaults will show large equal-and-opposite hops; those are the route, not the user's fill.
If the result is exactly one mint (or SOL) down and one mint (or SOL) up, you can describe the transaction as a swap of X A for Y B, and name the swap programs that ran. If a second asset also moved, or only one side is visible on the signer, the honest summary is to list the programs and the nets you do have.
The fee payer is not always the user. Some transactions have a relayer as account 0 (it pays the fee) and a second signer whose token accounts actually changed. Read the owner field on the token-balance rows.
A Jupiter multi-hop that does pair
On 15 November 2026 at 14:22 America/Fortaleza, signature 5Qnv6EbAQdyLWfnG9jyNM2dbpmg8L9yEFUj6pcuZYnpHsSNU4t9h5xQJcYG9xJcZUVMbenQmaZqPsePqddHv8ndV invoked Jupiter (JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4), pump.fun (6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P) and Meteora DLMM (LBUZKhRxPF3XUpBCjp4YzTKgLccjZhTSDM9YuVaPwxo). For the signer E2UJa6X5FxHPnDRzMkbjH9DqGwxnnEC5FDTXC9cgtMdM, the nets were a single pair: 268532.573207 of mint 6DRjrWDx82qvCHj6fDi6Hbhn2jKXm32zDyKk2k8Ppump out, and 0.025438228 SOL in. The fee was 0.000008503 SOL.
Rugsight's summary is "Swapped 268532.573207 6DRj…pump for 0.025438228 SOL via pump.fun and Jupiter and Meteora DLMM," plus the fee, the status, and two program ids it does not have a label for (6Vo3245eszAb5wuqEMw8mGdbfRUdKbHhDHP5LcaGuTAB and REALQqNEomY6cQGZJUGwywTBD2UmDT32rZcNnfxQ5N2). Those unknown programs are listed; they are not turned into a second swap story. The page is /tx/5Qnv6EbAQdyLWfnG9jyNM2dbpmg8L9yEFUj6pcuZYnpHsSNU4t9h5xQJcYG9xJcZUVMbenQmaZqPsePqddHv8ndV.
Several inner hops can still net to one in and one out for the signer. That is what "multi-hop" means here: the route used more than one venue, and the wallet still had a single pair of nets.
A direct Orca Whirlpool swap
In the same minute, signature 5yajpwauKynSKBg4GD4GsP9A5PoU7rz2qErNkB1rCiXCaFTSfdPLdAcL9rcaZQBHSKBzXcRDP416HhxmweNgvxUQ invoked Orca Whirlpool (whirLbMiicVdio4qvUfM5KAg6Ct8VwpYzGff3uctyCc) without Jupiter. The fee payer was AgmLJBMDCqWynYnQiPCuj9ewsNNsBJXyzoUhD9LJzN51. The tokens moved on a second signer, 8iCN2iksGk7rVhAoT42hYwwfTwdPd4LZf2yfSuSzD82: 9.296107 USDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v) out, and 81771.335638 of mint 8cWGfiHyKqxgLrLtkPt2NnLkSUV2JbcLBf4RN6Fapump in. The fee was 0.00041 SOL.
If you only looked at the fee payer's token accounts, you would miss the swap. Rugsight uses the fee payer when that wallet has a one-for-one pair, and otherwise a single other signer who does. The summary is "Swapped 9.296107 USDC for 81771.335638 8cWG…pump via Orca Whirlpool." One program id on the trace is unlabelled (DF1ow4tspfHX9JwWJsAb9epbkA8hmpSEAtxXy1V27QBH) and is listed as unknown. The page is /tx/5yajpwauKynSKBg4GD4GsP9A5PoU7rz2qErNkB1rCiXCaFTSfdPLdAcL9rcaZQBHSKBzXcRDP416HhxmweNgvxUQ.
Wrapped SOL on a Raydium route
Earlier the same day, at 00:40 America/Fortaleza, signature dtt7vwiWFzkwZLMfcZ5BVnrPFMfYc77zYV2Z6iaP5GssDWSrAHiYDfjyEfHE6EGF3rDYZdquYyfFdnmW1xxii7n wrapped SOL (syncNative on a temporary WSOL account), swapped through Raydium AMM (675kPX9MHTjS2zt1qfr1NYHuzeLXfQM9H24wFSUt1Mp8) and pump.fun AMM (pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA), and closed the WSOL account back to the signer 2qZR4cBqJfMmDpRn6Wy6t3ZNpcTpU5oVniAxATt96oxG. The signer's nets, after folding WSOL into SOL and excluding the 0.000125168 SOL fee, were 1.011 SOL out and 98301.090248 of mint 85RhcSEMy15SNhFLmSArNm7udPKXVagVgsq4YmSopump in. The extra 0.011 SOL above the 1 SOL that was wrapped is tips that still left the same wallet, so it remains one asset out.
The summary is "Swapped 1.011 SOL for 98301.090248 85Rh…pump via Raydium AMM and pump.fun AMM." It does not mention WSOL, because the wrap and unwrap cancelled at the asset level. The page is /tx/dtt7vwiWFzkwZLMfcZ5BVnrPFMfYc77zYV2Z6iaP5GssDWSrAHiYDfjyEfHE6EGF3rDYZdquYyfFdnmW1xxii7n.
When a one-sentence swap is not honest
Not every transaction that invokes Jupiter or Orca is a clean user swap. Rugsight then names the venues, lists the signer's nets, and says it could not fully describe the swap from the parsed instructions and balance changes. Examples from the same day:
- Signature
4ui56oZQYJYK1zHdjfCyfsvY9LLWx735ZaCd1778dbaD2yUfSwGHcLHQcRK4kWK3x3cvaTD1H2on8hfFvT1oatkJinvoked Jupiter, but the fee payer only received a residual 0.000120657 SOL (folded from WSOL). The large USDC and WSOL hops were on other accounts. - Signature
2T3i4m8U4iwAHRBAR1SL26xLqr222WCtbHmCNbWh9Jrq5T9Tg3LhxPkTEaw99vY5j8LAZusCSBqwQySeQA5bkQMkinvoked Orca Whirlpool and Meteora DLMM, and the fee payer only sold 20.013851 CASH. The rest of the route was on pool or router accounts.
A route can also fall back when the signer spent a token and a small amount of SOL (a tip or rent for a new associated token account) and received one token. That is two assets out and one in. The explainer does not drop the SOL to force a prettier sentence.
Unknown program ids stay unknown in both the paired and the fallback cases.
FAQ
How can I tell what I actually received in a Solana swap?
Read the signer's net token and SOL changes (fee excluded, WSOL folded into SOL), not the inner transfers between pool vaults. If exactly one asset went out and one came in, that pair is the fill. Rugsight prints it as "Swapped X A for Y B via …" on /tx when those nets pair.
Why does a Jupiter swap mention several programs?
Jupiter is an aggregator. A single user fill can hop through more than one venue (for example pump.fun and Meteora DLMM). The program list is the route. The signer's nets are still a single pair when the intermediate tokens do not rest in the user's wallet.
Why did Rugsight not summarise my transaction as a swap even though Jupiter ran?
Either the signer's nets were not exactly one asset out and one in, or the visible nets belong to accounts the signer does not own (a router or a pool). The explainer then names the venues and lists the nets it does have, rather than inventing a pair.
Does wrapped SOL mean I swapped SOL for a different token called WSOL?
Not by itself. Wrapped SOL is native SOL in a token account (mint So11111111111111111111111111111111111111112). A wrap or unwrap should net to zero once those two balances are combined. On the Raydium example above, the wrap is visible as a syncNative instruction, and the summary still reports a single SOL leg.