If a BNB Chain swap is pending, check its nonce and fee; if it failed, read the receipt before retrying. A pending transaction has no final on-chain result yet, while a failed one was included but its contract call reverted. That difference tells you whether to wait, replace the transaction, or correct the trade conditions.
Read the transaction status before acting
A pending transaction has been signed and broadcast, but it has not been included in a block. A failed transaction has been included: the chain processed it, recorded a receipt with a failure status, and charged a gas fee for the work attempted. Neither status alone tells you whether the swap’s token balance changed.
Start with the transaction hash in your wallet’s transaction history or a BNB Smart Chain block explorer. Check the sender address, nonce, block number, receipt status, and any decoded error or event details. A wallet view can help you compare activity with holdings: the PooCoin wallet view is one example of using wallet activity alongside token tracking. The transaction receipt is still the evidence of whether that particular swap succeeded.
“Pending” can mean the transaction is waiting in a node’s mempool, the temporary queue of transactions not yet included in a block. It can also mean your wallet has not refreshed its status. If an explorer cannot find the hash, the transaction may not have reached that explorer’s node, or it may have been dropped from a mempool. That does not prove it was canceled.
A pending transaction is usually blocked by its nonce or fee
Each account sends transactions in nonce order: the nonce is a sequential number attached to each transaction from that address. If nonce 12 is pending, a later transaction with nonce 13 generally cannot execute first. This is why one stuck transaction can make several later wallet actions appear pending too.
Check whether an earlier transaction from the same address is still pending. If so, resolve the earliest unresolved nonce first. Also check whether another wallet or device sent a transaction from that account; both can compete to use the same next nonce. Only one transaction with a given sender and nonce can be included successfully.
If the transaction is simply underpriced for current demand, you can wait or replace it with a transaction using the same nonce and a higher fee. For a dynamic-fee transaction, that means adjusting its fee cap and priority fee; for a legacy transaction, it means increasing the gas price. The replacement must meet the wallet or node’s acceptance rules, which can vary, and it still needs enough BNB to cover its gas limit at the new fee.
A “cancel” is another same-nonce transaction, often a zero-value transfer back to your own address. It is not a command that erases the first transaction. Whichever version is accepted and included first wins; if the original swap executes first, the cancellation cannot undo it. Check the original transaction’s status before trying again.
A failed swap usually reverted during contract execution
If the receipt says failed, the transaction is finished; raising its fee will not make that same transaction succeed. Gas was spent on execution, but a reverted swap normally leaves the swap’s token transfers unapplied. Look for the reason in the wallet or explorer’s decoded error, if available, rather than sending the same call repeatedly.
A common cause is that the trade’s minimum output was no longer achievable when it reached the contract. A quote is calculated from the pool’s state at one moment; other swaps can change that state before yours executes. If the actual output falls below the transaction’s minimum, the router reverts to enforce slippage protection. Recheck the quote, liquidity, and price impact, then set a minimum output you can accept. Higher slippage tolerance may help a volatile trade execute, but it also allows a worse price.
Other failures include insufficient BNB for gas, a token balance too small after accounting for earlier transactions, a missing BEP-20 allowance, or a token contract that rejects the transfer. An allowance is the amount of a token a contract is authorized to spend. If an approval transaction failed, the swap may fail too; check the approval’s own receipt rather than assuming it worked. A Rug check or liquidity review can inform whether a token is risky, but it does not explain a failed receipt by itself.
Retry only after you know which transaction won
Before retrying, confirm whether the original transaction is pending, failed, or successful. If it is pending, a second swap with a new nonce could execute after the first and buy twice. If it is failed, correct the cause first. If it succeeded, compare the receipt’s token transfers with your balances before making another trade.
For an unconfirmed transaction, decide between waiting and replacing based on urgency and the fee you are willing to spend. For a confirmed failure, keep the hash and note the revert reason; gas is not refunded simply because the swap failed. If the wallet and explorer disagree, verify the network and sender address, then check the same hash on another BNB Smart Chain explorer. PooCoin can provide context when reviewing token prices and wallet activity, but the chain receipt determines the transaction result.
In short, use the receipt to separate a queued transaction from a reverted one. Check the earliest pending nonce, replace only when you understand the same-nonce race, and fix a failed swap’s actual execution condition before retrying.