Start with the transaction identifier and network. A provider’s internal order number is not necessarily an onchain transaction hash.
Four clocks can be running
Scroll horizontally to read all columns.
| Stage | Evidence | Who can explain a delay |
|---|---|---|
| Withdrawal processing | Provider history and an onchain identifier, if broadcast. | Sending provider. |
| Network execution | Explorer status, block and token movement. | Wallet or network information; not a recovery agent. |
| Confirmation policy | Chain confirmations versus the recipient’s required threshold. | Receiving provider’s deposit policy. |
| Account credit or review | Recipient’s internal deposit record. | Receiving provider. |
No transaction hash yet
Check whether the sending service says the withdrawal is pending, reviewing or broadcast. If there is no network transaction, repeatedly refreshing a block explorer will not reveal an internal queue.
Use the service’s verified support channel and keep the order reference privately. Ask whether the withdrawal was broadcast and on which chain. Do not let a stranger turn a missing hash into a demand for a second deposit.
A selectable delay is a scheduling feature
A provider may advertise delayed payouts or a delay control. That is different from a transaction stuck in a queue. Its terms must explain when the delay starts, whether it can be cancelled and what happens if execution fails.
Neither a chosen delay nor an “instant” option demonstrates privacy or sets another platform’s credit time. StableScope does not offer payout scheduling or measure a service’s timer.
A transaction exists but the result is unclear
Open the identifier on the correct chain. An Ethereum explorer cannot establish the status of a TRON transfer. Check pending, failed or successful status, then inspect the actual token movement and destination.
Ethereum execution can consume gas even when it fails. A success label, by contrast, does not guarantee that an offchain exchange has credited the deposit. Network inclusion and a provider’s processing policy answer different questions.
Successful onchain, absent from the account
Do not assume that waiting longer can fix a wrong-token or wrong-network deposit. That requires a recipient-specific assessment, and recovery may not be available.
- Confirm the token contract and chain match the recipient’s deposit support.
- Compare the delivered amount with the recipient’s minimum deposit.
- Check its required confirmations and any deposit suspension notice.
- Check whether the receiving service has requested information through its official account interface.
- Send the transaction identifier and network to verified support; never send a seed phrase.
A countdown is not a settlement guarantee
A website can count down to a quote expiry or a scheduled action. It cannot thereby guarantee network execution, confirmations or another platform’s compliance review. A precise claim needs a definition of when the clock starts and what “complete” means.
StableScope does not show a universal processing-time estimate because we do not observe your transaction, provider queue or recipient policy. Use the actual stage evidence instead of a generic number.
Instant, fast and delayed are not the same claim
Scroll horizontally to read all columns.
| Claim | Question to ask | What remains unknown |
|---|---|---|
| Instant | Does it mean quote creation, broadcast, network inclusion or account credit? | The other stages and any review queue. |
| Fast | What start point and upper bound does the provider define? | Whether the destination has a different confirmation threshold. |
| Delayed | Is the delay caused by a provider queue, network status, confirmations or recipient review? | Whether repeating the send would help or increase exposure. |
| Three-second handoff | Is it only a navigation timer before leaving a site? | It says nothing about a blockchain settlement or provider result. |
Use the exact stage evidence instead of repeating a speed adjective. StableScope does not promise instant, fast or guaranteed processing for a transaction it cannot observe.
Sources & review
Editorial review: Sep 21, 2026. Source-specific dates and retrieval limits are stated where relevant. Issuer and service statements are attributed, not independently audited; a citation is not an endorsement.
- Ethereum · Block explorers (opens in a new tab)
Public transaction, token and account fields.
- Ethereum · Gas and fees (opens in a new tab)
Gas units, ETH fees and execution failure.