What "pending" actually means
Pending is the window between broadcasting a transaction and the network treating it as final. In that window the transaction sits in the mempool, a holding area of transactions that have been announced but not yet included in a block. Validators or miners pick transactions out of the mempool, place them in a block, and then further blocks build on top before most services call the transaction settled.
So "pending" is not one state. It can mean your transaction has not been included in any block yet, or that it has been included and is now waiting for the follow-on confirmations a receiver requires. Those are different problems with different fixes, which is why the first useful step is almost always to look up the transaction hash on a block explorer and see which of the two you are in.
Pending looks different on each network
How long "normal" lasts depends entirely on the chain, because block times and confirmation conventions vary widely. What feels stuck on one network is routine on another.
- Bitcoin: blocks arrive roughly every ten minutes on average, and many receivers wait for several blocks before crediting a deposit. A wait measured in tens of minutes can be completely normal here.
- Ethereum mainnet: blocks are frequent, but a transaction priced with a low fee can wait behind higher-fee ones when the network is busy. Inclusion is usually quick when your fee is competitive.
- Fast Layer-1 and Layer-2 networks: confirmation is often a matter of seconds to a couple of minutes when the network is healthy.
- Tron and Solana: high throughput means base confirmation is typically fast, though a congested moment can still add delay.
Cross-chain swaps have a second leg
A same-chain swap confirms once. A cross-chain swap has two settlement events. First the source transaction confirms on the network you sent from. Only then does a routing engine act on the destination chain to release the asset you are receiving. That design is normal and unavoidable, because no single transaction spans two independent networks.
The practical effect is that a cross-chain swap can read as pending while one side is already finished. The source may have confirmed minutes ago while the destination leg is still waiting for its own network to settle. Reading a single "pending" label without checking both sides is the most common reason people think a swap is stuck when it is simply mid-route.
When to wait and when to act
Start by comparing elapsed time against the network involved, not against your patience. A few minutes on a fast chain is nothing. On Bitcoin, waiting on confirmations can legitimately run longer. If the swap has been pending well past the typical time for those networks, open the source transaction on a block explorer using its hash. That single check tells you which side is stuck.
If the source transaction never confirmed, the problem is on the send, not the swap. A low fee or a nonce issue can leave it lingering in the mempool, and depending on your wallet you may be able to speed it up or cancel it. If the source confirmed but the destination has not arrived after a reasonable window for that chain, that is the moment to contact support with the transaction hash rather than sending a second time. Resending before you have checked can create a duplicate transaction and a second cost.
- Find the transaction hash in your wallet or the swap confirmation screen.
- Paste it into the block explorer for the source network and confirm the number of confirmations.
- If it is a cross-chain swap, check the destination network separately.
- Wait if confirmations are still accruing. Contact support with the hash if the source is confirmed but the destination has not appeared.