If you have sent crypto and the balance has not moved, the cause is almost always the blockchain rather than the wallet. This article explains what determines the wait and what to check while it runs.
Published September 29, 2026 · 2 min read
The typical range is from a few minutes to about an hour. That time is the network confirming your transfer. A wallet only sees the deposit once the required confirmations are reached, and then credits it automatically. In Nexus Pay, for example, there is nothing to approve or request: the balance updates on its own after the network confirms.
Blockchains confirm transactions at different speeds, so a coin such as USDT can take less time on one network than on another. USDT and USDC can be sent over TRC-20, ERC-20, BEP-20 and TON, and each of these is a separate blockchain with its own pace. Speed is not the only difference: the network also determines the fee you pay to send. If you have a choice and both sides support several networks, compare the speed and fee before you send, then make sure the address matches the network you picked.
Yes. A congested network confirms transactions more slowly, and at the same time it can charge a higher network fee. So a busy period can make a transfer both slower and more expensive than usual. This is a property of the blockchain at that moment, not something the receiving wallet can speed up.
Confirmation time is counted from when the transaction is actually broadcast on-chain, not from when you press send in the other app. If the sending service queues, reviews or batches withdrawals first, that time comes before the network even sees the transfer. So a deposit that looks late may simply not have reached the blockchain yet. The transaction hash from the sending side is the way to tell: once you have it, you can follow the transfer on the network.
| Factor | Effect on the wait | What you can do |
|---|---|---|
| Choice of network | Each blockchain confirms at its own pace, so the same coin can be faster or slower | Compare the networks both sides support before sending |
| Network congestion | A busy network confirms more slowly and can charge a higher fee | Allow extra time; the deposit is still credited automatically |
| Broadcast moment | The clock starts when the transaction reaches the blockchain, not when you press send | Get the transaction hash from the sending service and check that it was broadcast |
| Wrong network or amount below minimum | The deposit does not arrive, or is not credited | Match the network to the address and check the minimum in the app before sending |
Go through the basics before assuming a delay:
If all three are fine, the most likely explanation is ordinary confirmation time, and the deposit will be credited automatically when it completes.
Not after the transfer is sent: confirmations depend on the blockchain, and blockchain transfers are irreversible. What you can influence is what happens before you send. Choose a network you have checked, send a small amount first if you are unsure, and avoid starting a transfer you need urgently at the last minute. Nexus Pay shows the supported networks and their minimums in the app, so you can check these details before sending.
In Telegram, in a minute, with no paperwork.
Open Nexus Pay
Opening…