The transfer is stuck: what actually helps

Updated 22 September 2026 · compiled by the editorial team from the services' own pages

«Stuck» almost always means the network, not the service. A transfer sits until it gets confirmations, and under load that takes longer than the estimate on the quote screen.

1. Find the transaction in an explorer by its hash. If it is not there, it never left your wallet — the problem is on your side and the coins are safe.
2. Look at the confirmation count. A transfer waiting for confirmations is working, just slowly; nothing on the service side can speed it up.
3. Check the fee you paid. A low fee at a busy hour is the usual reason a transaction sits for hours.
4. Write to support with the hash. Without it nobody can help; with it the answer is usually one message long.

What does not help: sending the amount again. Two transfers mean two swaps, and the second one is not a fix for the first.

Check before you send

• The transaction is visible in a block explorer — if it is not, it never left your wallet.
• The confirmation count is growing — a transfer with confirmations is working, just slowly.
• The fee you paid is not below the current network level — a cheap fee at a busy hour is the usual reason for the wait.
• The hash is in the message to support — without it nobody can look anything up.

Mistakes that cost the most

• Sending the amount again. Two transfers mean two swaps, not a fix.
• Cancelling the order while the coins are on the way. The swap still has to be settled by hand afterwards.
• Writing to support before the first confirmation. There is nothing on their side to see yet.

Questions

How long is too long?

Longer than the chain's own confirmation time plus the service's stated window — before that the wait is normal.

Can support speed up the network?

No. They can rebroadcast or settle manually, but confirmations are the chain's work.

Services that support this