Which Clock Is Running: Blockchain Confirmation or Exchange Processing?

A deposit that has been pending for hours can be normal on one route and abnormal on another. Measure two clocks separately. The blockchain clock starts when a valid transaction is broadcast and ends when the exchange’s required confirmation depth is reached. The exchange clock starts at that point and ends when the platform credits or releases the balance. Support should receive the clock that has stopped, not only the total elapsed time.

Create the timeline before deciding that hours are excessive

Record the withdrawal request time, TXID appearance time, first block time, current confirmations, exchange-required confirmations, exchange status and last status change. Use one time zone. A six-hour delay with a growing confirmation count differs from six hours with no TXID.

Use the Two-Clock Deposit Timeline

Only one clock should control the next action.

• Clock 0 — sender processing: withdrawal requested but no valid TXID
• Clock 1 — blockchain: TXID exists but required confirmations are incomplete
• Clock 2 — exchange ledger: required confirmations are complete but account credit is pending
• Exception track — wrong route, missing memo, below minimum or unsupported asset
• Review track — maintenance, KYC, sender-information or manual hold

Clock 0 — no TXID means no exchange deposit is visible on-chain

The sending exchange, wallet service or reward platform still owns the request. Ask it for the transaction hash and broadcast status. The receiving exchange cannot credit a blockchain deposit that has not been published.

Clock 1 — confirmations are still accumulating

Open the correct explorer and compare the current count with the exchange requirement. Network congestion, a low sender fee or slow block production can extend this clock. Coinbase notes that pending transactions can result from network volume, insufficient fees or temporary synchronization problems.

Use the exchange’s expected processing table

Kraken currently publishes asset-specific confirmation counts and estimated times; its Bitcoin example is four confirmations, approximately forty minutes under ordinary ten-minute blocks. This is an exchange-specific baseline, not a promise for every BTC deposit or current network condition.

Clock 2 — the chain requirement is complete

Now inspect the exchange deposit history. A status such as Credited, Completed, Pending or On hold describes the internal ledger, not the blockchain. Record when the required confirmation was reached and how long the platform has controlled the remaining delay.

A credited balance can still have a withdrawal hold

Some platforms distinguish trading availability from withdrawal availability. Kraken’s current status documentation says Credited funds can be used for trading while withdrawals remain unavailable until Completed. Do not confuse a post-credit security hold with a missing deposit.

Check the official service status

Wallet maintenance, node synchronization or a listed incident can delay many users. Save the status-page entry and avoid repeated tickets while the platform publishes an active incident. Recheck after the announced resolution.

Move to the exception track when the clock is not the real problem

A wrong network, missing memo, unsupported token or below-minimum amount will not be repaired by waiting. Compare the original deposit instructions with the TXID. Route errors need recovery assessment, not another hour.

Move to the review track when the account asks for action

Coinbase documents deposits pending until identity verification or sender information is supplied. A legitimate request should appear in the authenticated account. Complete only the minimum official requirement and keep a record of submission time.

Worked blockchain-clock case

A BCH deposit has a valid TXID, and the receiving exchange requires fifteen confirmations. After two hours it has twelve and the count is increasing. The exchange clock has not started. Waiting is rational while the transaction progresses.

Worked exchange-clock case

An ETH deposit met the required confirmations at 11:20, the network and address match, and the exchange status has remained Pending until 16:20 with no incident notice. The support request should state that the internal-processing clock has been stopped for five hours.

Escalate from evidence, not a universal hour count

Contact the sender when Clock 0 exceeds its published withdrawal window. Contact the receiver when Clock 2 exceeds its published processing expectation or shows On hold. If no expectation exists, provide the complete timeline and ask which internal stage remains unresolved.

Do not send another deposit as a timer test

A second transfer can be delayed by the same incident or can introduce a second route record. It also risks repeating an address, memo, network or minimum error. Diagnose the original transaction first.

Build the timeline support packet

Include the sending withdrawal ID, TXID, asset, network, amount, recipient, memo, first block time, current confirmations, required confirmations, exchange status, last change, status-page result and all authenticated account requests.

The waiting rule

Wait while the controlling clock is visibly progressing within a documented range. Escalate when progression stops, the required stage has completed without the next state, or an exception or review condition appears.

Timing sources reviewed on July 30, 2026

Current exchange documentation supports the separation between network confirmation and internal processing. Every estimate remains asset- and platform-specific.

• Kraken crypto deposit processing times: https://support.kraken.com/articles/203325283-cryptocurrency-deposit-processing-times
• Kraken current deposit status meanings: https://support.kraken.com/articles/360000674066-cryptocurrency-deposit-statuses
• Coinbase pending transaction causes: https://help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/why-is-my-transaction-pending
• Coinbase pending unconfirmed exchange deposits: https://help.coinbase.com/en/exchange/crypto-transfers/deposit-pending-unconfirmed-transaction
• Binance uncredited and maintenance causes: https://www.binance.com/en/support/faq/detail/115003736451
• Kraken missing-deposit checklist: https://support.kraken.com/articles/360001488126-cryptocurrency-deposit-is-missing

FAQ