How to Check a Pending BNB-to-Polygon Swap

To check a pending BNB-to-Polygon swap, follow its source transaction first, then check whether the route has submitted a transaction on Polygon. A cross-chain route can involve separate source and destination transactions, so one hash may not show the whole transfer.

The key is to identify which stage is waiting before retrying or taking any recovery action.

Where do I find the source transaction status?

Open the transaction details in the wallet or swap interface and copy the source-chain hash. Search that hash in BscScan if the source is BNB Smart Chain; use the relevant explorer if the interface specifies another BNB network. BscScan reports the on-chain transaction result, while the wallet’s pending label may simply reflect that it has not yet updated.

Check whether the transaction is pending, successful, or failed, and inspect its receipt and logs. A pending transaction has not been included in a block; a failed transaction has a recorded execution failure. A successful source transaction confirms that the source-side call executed, but does not by itself confirm delivery on Polygon. If the route uses a QuickSwap pool for a swap leg, that pool activity is distinct from the bridge or cross-chain settlement. For a separate treasury-routing question, see these QuickSwap routes for treasury transfers.

How do I check whether Polygon received the swap?

Once the source transaction succeeds, look in the route’s activity or status view for a destination transaction hash. Search that hash on PolygonScan and check its execution status, token transfers, and recipient address. A successful Polygon transaction should show the destination-side action and the asset delivered; confirm the token contract and amount rather than relying only on a wallet balance display, which can lag or omit an unlisted token.

If there is no destination hash yet, the route may still be waiting for its cross-chain message, relay, or settlement step. The source explorer cannot report that destination stage. Use the transaction or route identifier shown by the swap interface to check its own status, and compare the destination address and token with the quote or transaction details.

What should I do if the swap is still pending?

Classify the status before acting. The same “pending” label can describe different points in the route, and the appropriate next step depends on which one is unresolved.

• No source transaction found: Check that the hash and selected source network are correct. If the wallet never broadcast a transaction, there may be no on-chain transfer to track.
• Source transaction pending: Check its status in the source explorer and follow the wallet’s supported replacement or cancellation flow if one is available. Do not submit another swap simply because the interface has not refreshed.
• Source succeeded, destination missing: Check the route’s status using its tracking details. Keep the source hash and any route identifier for support or recovery.
• Destination transaction failed: Read its receipt and logs to establish whether any asset transfer completed. Follow the route provider’s documented recovery process before attempting another transaction.

Which details should I keep for a status check?

Keep the source hash, source and destination networks, receiving address, token contracts, and any route or order identifier. Share these through the route provider’s official support channel if the route remains unresolved. Never provide a seed phrase or private key; transaction hashes and public addresses are enough to investigate on-chain activity.

The practical rule is to treat source confirmation and destination delivery as separate checks. A completed source transaction is evidence of execution on BNB Chain; only the destination transaction and transfer records establish what arrived on Polygon.