On BNB Smart Chain, a swap can be included in a block in under a second, but wallet and network delays mean a pending transaction may take longer. If it has not cleared after about a minute, check its status before trying again; a swap marked failed needs a different fix from one still waiting.
If you are moving from pair research to a trade, how to spot newly active PooCoin pairs covers finding those pairs. This article picks up at the transaction stage: a newly active pair can still have too little liquidity, or a token can prevent a swap from completing.
Why is the swap still pending?
A pending transaction has been broadcast but has not yet been included in a block. BNB Chain documentation describes blocks arriving roughly every 0.45 seconds, but that is not a promise that every transaction will be included immediately: a low fee, a busy network, or a wallet’s connection to its RPC node can delay what you see.
Transactions from one wallet use a sequence number called a nonce. If an earlier transaction with a lower nonce is stuck, a later swap can wait behind it. Check the transaction hash on BscScan: if it has no receipt, it is still pending or has dropped from the node’s view; if it has a receipt, read the result before acting.
What does a failed swap mean?
A failed swap was included in a block, but its contract call reverted or ran out of gas. The swap did not complete, yet the network fee for the gas used is still charged in BNB. This is different from a pending transaction, which has not executed on-chain.
For a swap through PancakeSwap, “INSUFFICIENT_OUTPUT_AMOUNT” usually means the quoted output changed beyond your slippage tolerance, or the pool cannot provide enough output. PancakeSwap’s troubleshooting documentation also points to low liquidity as a cause. For example, if you set 1% slippage and the price moves 1.2% before execution, the swap may revert. A BEP-20 token can also impose transfer rules that prevent a trade.
What should you do before retrying?
Use the transaction’s on-chain status to choose the next action. Here is a practical sequence:
- Look up the hash on BscScan. Check whether it is pending, confirmed, or failed, and note its nonce. Do not submit the same swap again while the first one might still execute.
- If it is pending, check earlier transactions from the same wallet. Resolve the oldest pending nonce first. If your wallet offers replacement, it can rebroadcast that nonce with a higher fee; a cancellation transaction competes for the same nonce, so the original could still win.
- If it failed, read the revert reason and receipt. For low output or slippage errors, compare the current quote and pool liquidity, then consider a smaller trade or a modestly higher tolerance. A higher tolerance permits a worse execution price, so check the maximum you would accept.
- Recheck the pair before sending again. Compare the token address and liquidity, not only recent activity. For example, a pair showing a fresh trade but only $200 of available liquidity may not support your planned $500 swap without substantial price impact. PooCoin can help you inspect token prices and trading activity as part of that check.
In practice, I would retry only after the old transaction is confirmed as failed or replaced and the reason for failure is understood. Before acting, ask yourself: do I know whether the first transaction can still execute, and is the pair’s available liquidity enough for my trade?