A trader executes a swap on Solana, receives a confirmation, and sees the transaction marked successful. Yet when comparing the quoted price to the actual execution price, the difference exceeds what the DEX interface showed. This discrepancy—whether from market movement, fee structures, or deliberate manipulation—cannot be resolved by trusting the swap confirmation alone. The only way to verify what actually happened is to examine the transaction’s on-chain record: the exact tokens moved, their amounts, the price paid per unit, and the sequence of state changes recorded on the blockchain.
Solscan, the official and leading blockchain explorer for Solana, provides the raw data needed to reconstruct every detail of a swap execution. By learning to read transaction logs, identify token movements, and calculate the true price paid, traders can detect when a quoted price diverges from reality by more than slippage tolerance should allow. This skill transforms a passive user who accepts whatever the wallet shows into an informed participant who can verify execution quality and identify when a platform or routing protocol is working against their interests rather than for them.
Understanding the layers of a Solana swap transaction
A swap on Solana is not a single atomic operation visible as one line item. It is a sequence of instructions executed within a single transaction block. When a user initiates a trade through a DEX interface, the frontend constructs a transaction that may include token approvals, routing logic, fee deductions, and the actual token exchange. Each instruction modifies state on the blockchain, and each state change is recorded in the transaction’s instruction logs and token transfer records.
The first layer is the transaction structure itself. Every Solana transaction has a signature—a unique identifier used to reference it on the blockchain. Solscan makes it easy to access Solana blockchain data by allowing a user to search by that signature and retrieve the complete execution record. The explorer displays the transaction status, timestamp, fees paid, accounts involved, and a detailed breakdown of every instruction executed in sequence.
The second layer is the instruction execution log. Each instruction in a transaction generates a log entry that can indicate success, failure, or side effects. A swap instruction that claims “execution complete” may still have executed at an unfavorable price or routed through an unexpected path. The log text alone does not provide amounts or prices; it provides only the program’s interpretation of what occurred. Relying only on instruction logs and status codes is therefore insufficient.
The third layer is the token transfer record. This is where slippage and price impact become measurable. When a swap occurs, tokens move from the user’s wallet to a liquidity pool or router, and different tokens move out. The amount sent, the amount received, the token types, and the accounts involved are all recorded as discrete token transfer events. These transfers are the ground truth: they represent actual state changes on the blockchain, immutable and verifiable by anyone who examines the chain.
Locating and interpreting token transfer logs
On Solscan, open a completed swap transaction using its signature. Below the transaction header, find the “Token Transfers” or “Transfers” section. This section lists every movement of SPL tokens during the transaction in chronological order. Each entry shows the token type, the sending address, the receiving address, the amount transferred, and the decimal adjustment needed to display it in human-readable form.
For a simple SOL-to-USDC swap routed through a single DEX, the token transfers might appear as two events: one showing USDC leaving the user’s associated token account and entering a liquidity pool or router contract, and another showing USDC leaving the pool and entering the user’s USDC account. If the route is more complex—for example, SOL to USDC through an intermediate token—additional transfers appear, each representing a hop in the path.
The decimal adjustment is critical. Most Solana tokens use decimal places to represent fractional units. USDC, for instance, uses 6 decimals, meaning a transfer of 1,000,000 units represents 1 USDC. If Solscan displays a transfer as “1000000” without adjusting for decimals, the user must divide by 10^6 to get 1 USDC. Some explorers show both the raw amount and the formatted amount; others display only the raw value. Misreading this layer is one of the most common errors in manual price calculation.
Identify the two transfers that represent the core swap: the token you sent out and the token you received. Note the exact amounts for both. Do not assume that the amount received is final; if the transaction includes multiple hops, intermediate transfers may also appear. The most direct approach is to identify the first transfer of your input token (leaving your wallet) and the last transfer of your output token (entering your wallet). Everything in between is routing, liquidity provision, fee collection, or other protocol mechanics.
Calculating execution price from on-chain amounts
With the input amount and output amount identified, the execution price is straightforward arithmetic. If you sent 100 SOL and received 5,000 USDC, the execution price was 5,000 ÷ 100 = 50 USDC per SOL. This is the true price paid, before any interface display, before the DEX’s own quotes, and regardless of what the wallet showed before you approved.
Execution price differs fundamentally from quote price. The quote price is what the DEX interface displayed before you signed the transaction—typically an estimate based on the current state of liquidity pools and the size of your trade. The execution price is what you actually paid, calculated from the immutable transaction record on the blockchain. These two prices can differ for several reasons: market movement between quote and execution, slippage absorbed by your configured tolerance, routing through an unexpected path, or fees deducted by the protocol or aggregator.
To isolate slippage and price impact, calculate the difference between quoted and executed prices. If the DEX quoted 50.2 USDC per SOL and you executed at 50 USDC per SOL, that is 0.2 USDC per SOL of negative price movement—roughly 0.4% slippage. Slippage caused by market movement is expected and is why users set a slippage tolerance. Slippage caused by poor routing or fee extraction is not.
The calculation becomes more complex when the transaction includes multiple token hops. If the route was SOL to ORCA (Orca token) to USDC, you must calculate the intermediate prices. SOL to ORCA shows the ORCA-denominated price of SOL; ORCA to USDC shows the USDC price of ORCA. To find the effective SOL-to-USDC price, multiply those intermediate prices. If the product differs significantly from the market price of SOL in USDC, the route was inefficient or extractive relative to a direct swap.
Identifying fees, routing inefficiencies, and extraction points
Transaction fees on Solana are paid in SOL and are distinct from swap fees. The “Fee” field near the transaction header shows the network rent paid to validators—typically 5,000 lamports (0.000005 SOL) for a standard transaction. This is negligible in most cases. But DEXes also charge swap fees, often 0.25% to 0.5% of the trade value, and these fees are embedded in the price movement rather than displayed separately on Solscan.
To estimate the DEX fee’s impact, compare your execution price to the spot price of the pair at the moment the transaction was confirmed. If Solscan shows the transaction confirmed at block 100, and the on-chain price of SOL in USDC at that block was 50.3 USDC per SOL, and you executed at 50 USDC per SOL, the difference is 0.3 USDC per SOL. Part of that difference is likely DEX fees; the remainder is your share of price impact from the trade size relative to liquidity depth.
Routing inefficiencies become apparent when comparing single-hop and multi-hop execution prices. If a SOL-to-USDC direct swap quotes at one price but a SOL-to-ORCA-to-USDC routed swap executes at a worse price, the routing added cost. This can occur when a routing algorithm prioritizes a path with higher liquidity in one leg but poor pricing in another, or when it uses pools with higher fee tiers. Identifying the route from Solscan requires reading the instruction log or token transfer sequence to understand which programs (DEXes) were involved.
Extraction occurs when a platform, aggregator, or MEV searcher intercepts your transaction and executes it in a way that benefits them at your expense. Examples include sandwich attacks (a searcher places a transaction before and after yours to move the price against you), MEV extraction (a validator includes other transactions in a block to front-run your trade), or fee manipulation (a routing contract charges unexpected fees not disclosed by the UI). On-chain analysis cannot directly prove intent, but it can reveal the abnormal price movement or missing value that suggests extraction occurred.
Reconstructing complex routes and multi-hop swaps
When a single swap triggers multiple token transfers, the transaction is executing a route. Aggregators like Jupiter or Orca’s routing protocol may break a SOL-to-USDC trade into SOL-to-mSOL-to-USDT-to-USDC if that path offers better liquidity or lower total fees. Solscan displays these as separate transfer events, and reconstructing the route requires reading them in sequence.
Open the “Instructions” tab on the transaction page. This shows every program call made during the execution. For a multi-hop swap, you will see multiple program invocations, each corresponding to a different DEX or routing stage. Note the program names (e.g., “Orca”, “Raydium”, “Jupiter Swap”) and cross-reference them with the token transfers. If an ORCA instruction executed and was immediately followed by a token transfer from Orca’s liquidity pool to your wallet, that transfer belongs to the ORCA swap.
To calculate the true price of a multi-hop route, treat each hop as a separate trade and calculate its price. Then evaluate whether the sequence of prices makes sense relative to market conditions. If SOL-to-mSOL executed at a 1% premium to spot price, mSOL-to-USDT at a 2% discount, and USDT-to-USDC at 1:1, the overall path cost you 2% plus accumulated slippage—significantly more than a direct SOL-to-USDC route would cost at the same timestamp.
Some routers automatically attempt multiple paths in parallel or split volume across pools to find the best execution. When a transaction includes dozens of transfers or dozens of instructions, it is often attempting multiple routes simultaneously and selecting the best result. Manually reconstructing such a transaction is tedious, but the exercise clarifies why a given route was chosen and whether the routing logic acted in your favor or against it.
Detecting sandwich attacks and MEV extraction
A sandwich attack occurs when a searcher or validator observes your pending swap transaction, places their own transaction before it (front-running), then places another transaction after it (back-running), capturing the profit from the price movement they forced. On Solscan, sandwich attacks often appear as clusters of transactions from the same address or MEV searcher contract, with your transaction in the middle.
To identify a suspected sandwich, examine the transactions immediately before and after your swap in the same block. Solscan displays transactions in block order, so if your swap is at position 15 in a block and a transaction from a known MEV contract is at position 14, check whether that earlier transaction moved the price of your pair. If it bought a large amount of the token you were selling, it front-ran you. If a transaction at position 16 sells that same token immediately after your execution, it back-ran you, locking in the profit from the price movement.
The cost of a sandwich is visible in your execution price. If you executed at a significantly worse price than the spot price immediately before the front-run transaction, the difference is largely the MEV extraction. If you executed at a significantly better price than the spot after the back-run transaction, you benefited from the movement—a rare outcome that suggests a coincidental favorable price movement rather than intentional extraction.
Solana’s leader-based consensus and high block production rate reduce but do not eliminate sandwich attacks compared to Ethereum. A transaction can still be observed in the memory pool (the set of pending transactions) and inserted into a block by a validator who is constructing the next block. Monitoring the memory pool for your transaction’s signature is difficult for ordinary users, but examining confirmed transactions on Solscan is straightforward. If you notice a pattern of consistently worse-than-expected execution prices, request real-time transactions data via Solscan’s transaction tracking feature to compare quote times against execution times and see if timing correlates with price slippage.
Using Solscan APIs and tools for systematic verification
For traders who execute swaps frequently, manual inspection of each transaction is not sustainable. Solscan provides a read-only API allowing developers and advanced users to query transaction data programmatically. The API can retrieve token transfer events, instruction execution logs, account balances, and historical price data for token pairs. By writing a simple script, a trader can automatically calculate execution prices for every swap and flag transactions where slippage exceeded expectations or prices deviated from market rates.
The Solscan API is free, does not require authentication, and returns data in JSON format suitable for analysis in spreadsheets or programming environments. Common queries include retrieving all transactions from a specific wallet address within a date range, finding all token transfers of a particular token, or retrieving the balance history of an account. A trader building a personal audit trail might query their wallet address to retrieve all swap transactions from the last month, then use the token transfer data to calculate execution prices and identify outliers.
Another approach is to use the Solscan web interface to export transaction history. While not as flexible as the API, exporting data from Solscan into a spreadsheet allows a trader to organize and analyze multiple transactions. The wallet analysis tool on Solscan can also display token holdings, transaction history, and token value over time, providing context for the execution analysis.
For traders who use a DEX aggregator or bot trading system, systematic verification serves another purpose: it provides evidence if disputes arise with the platform or if regulatory inquiries demand documentation of execution quality. On-chain data from Solscan is cryptographically verifiable and cannot be altered retrospectively, making it the definitive record of what occurred. Screenshots of interface quotes are not sufficient; the transaction signature and its on-chain record are.
Building a personal framework for acceptable execution quality
Knowing how to calculate true slippage is half the skill; the other half is defining acceptable execution quality based on trade size, market conditions, and liquidity. A 0.5% slippage on a small retail swap during volatile conditions is normal and reflects real price movement plus minimal fee extraction. A 2% slippage on a small trade during calm conditions suggests a problematic route or manipulation. A 0.1% slippage on a large institutional trade may indicate excellent routing; a 0.5% slippage on a large trade might indicate poor route selection or significant MEV extraction.
Build a personal baseline by calculating execution prices for 10–20 of your recent swaps. Plot the slippage or price impact against the trade size and market volatility at execution time. This establishes a reference distribution: what is normal for you given your typical trade patterns. When a future trade falls outside that distribution, the Solscan record provides evidence to investigate why.
Consider also the DEX or routing platform you used. Some routes consistently execute better than others because of higher liquidity, better pool fee structures, or more efficient algorithms. Orca, Raydium, Jupiter, and other platforms have different characteristics. By analyzing your transaction history by platform, you can identify which platforms serve your trade profile best and adjust future route selection accordingly.
Lastly, correlate execution quality with the settings you chose. If you set low slippage tolerance (e.g., 0.1%), you will see more failed swaps that fail to execute because the price moved beyond your tolerance. If you set high tolerance (e.g., 2%), you may execute but sacrifice price quality. Tracking your own rejection rate versus execution rate, plotted against slippage settings and market conditions, reveals the tolerance level that balances execution certainty with price quality for your needs.
Frequently asked questions
How do I find my swap transaction on Solscan?
Use the transaction signature provided by your wallet after you confirm the swap. Enter the signature into Solscan’s search box at the top of the page, or navigate to your wallet address and find the transaction in your history. Solscan displays real-time transactions, so the transaction typically appears within seconds of confirmation.
What is the difference between execution price and quote price?
Quote price is the estimated price shown by the DEX interface before you approve the transaction. Execution price is the actual price you paid, calculated from the immutable token transfers recorded on the blockchain. The difference is slippage and price impact, which result from market movement, fee deduction, routing inefficiency, or MEV extraction.
Can I detect if I was front-run or sandwiched using Solscan?
Yes. Examine the transactions immediately before and after your swap in the same block using Solscan’s block view. If a transaction from a known MEV contract moved the price of your token pair before your swap, and another transaction sold the same token immediately after, you were likely sandwiched. Compare your execution price to the spot price before the front-run transaction to estimate the extraction cost.
