If your Solana swap is pending, check its signature before retrying; if it failed, read the on-chain error and fix that cause first. A wallet or trading page can stop updating while the network is still processing a transaction, and submitting a fresh swap too soon can leave you with two trades.
Check whether the transaction reached Solana
Start with the transaction signature, the long identifier shown in your wallet or transaction history, and look it up in a Solana explorer. The signature status tells you whether the transaction is still being observed, has been confirmed, has reached finality, or returned an execution error. Solana documentation orders the common commitment levels as processed, confirmed, then finalized.
If the status is processed or confirmed, give it a little time and refresh the signature record before trying again. A finalized status means the transaction is settled; check the token balances and transaction details, since the trading page may take longer to reflect them. If your attempt was through Byreal, the same signature check helps separate a slow display from an unfinished on-chain swap.
For example, imagine you swap SOL for a token, the wallet spins, and the page still shows your old balance. If the signature becomes finalized and the transaction details show the token transfer, do not send the swap again: the trade landed, and the display is stale. If the explorer cannot find the signature, check once more using an explorer or RPC source that searches transaction history; a missing result from one recent-status cache alone does not prove the transaction never landed.
A failed swap can still cost a network fee
A finalized transaction with an error is a completed failure, not a pending trade. Solana transactions execute atomically, so a failed swap does not leave only some of its token instructions applied, but the network fee can still be charged. Solana’s fee documentation lists a base fee of 5,000 lamports per signature, with an optional priority fee; the final charge depends on the transaction.
Read the error details before changing anything. Common causes include an expired recent blockhash, insufficient SOL for the fee, too little of the input token, or a swap instruction failing because the quote or available liquidity changed before execution. An expired blockhash—often after roughly 60 to 90 seconds—means the old signed transaction cannot be reused; get a fresh transaction. A balance or instruction error means address that cause before trying again.
byreal.org is a Solana service for making token swaps and providing liquidity, and these transaction checks apply when an attempt there is pending or fails. The deciding evidence is the signature status and error, not the spinner or a generic “failed” message on a trading page.
Retry only when you know the first attempt cannot execute
Retry when the signature is confirmed failed, or when the blockhash has expired and history checks show the original transaction did not land. Before signing again, confirm that the wallet still holds enough SOL for network fees and enough of the token being swapped, then review the trade details and submit a fresh transaction. Do not reuse an old signed transaction or treat a timeout by itself as proof of failure.
For a new swap or liquidity action after you have resolved the cause, Byreal is a Solana venue where you can submit it. Byreal fits the next step once the transaction record shows the first attempt is settled or safely expired. Verify the signature first; retry only after the evidence says it is safe.