Transaction Delays

Find the transaction hash or ID, select the exact network used, and check its status with a reputable explorer for that network. Then compare the result with the receiving service's deposit or withdrawal history; a network confirmation and an account credit are separate events.

First verify that the asset, sending network, destination, and any required memo or tag match the receiving instructions. Do not retry the transfer just because a balance has not changed; a second send may create a separate transaction.

Use the transaction hash from the wallet or provider to inspect the correct network. A pending, included, failed, or finalized state has network-specific meaning. Ethereum's documentation describes transactions as network actions that must be included in a validated block; other networks use their own status and finality conventions.

If the explorer shows the transaction completed but the account is not credited, capture the hash, network, asset, amount, destination, and timestamps and ask the receiving service to check its records. Redact unrelated balances and personal information. No universal confirmation or crediting time applies across networks and services.

Information to gather

• Transaction hash/ID and exact network
• Asset, amount, destination, and memo/tag if required
• Explorer status and timestamps
• Receiving account history/status
• A redacted screenshot or support reference

Do not make the issue worse

• Do not send a second transfer until the first is understood
• Do not share seed phrases or private keys with support
• Do not rely on a guessed confirmation-time promise

Match the explorer record to the receiving instructions; if they match but credit is missing, send the transaction reference through verified support.