A transaction can leave your wallet without immediately appearing in the recipient\u2019s balance. To understand the delay, follow the terms below in order: identify the asset and network, locate the transaction ID, check whether the transaction entered a block, and then separate blockchain confirmation from the recipient\u2019s own processing.<\/p>\n
The useful sequence is:<\/p>\n
This chain explains why \u201csent\u201d and \u201creceived\u201d are not always simultaneous. A wallet can create the transaction, the network can confirm it, and the recipient can still be completing a separate crediting step.<\/p>\n
A wallet can display a transaction attempt before enough network nodes have received it. If the TXID does not appear in an appropriate explorer after checking that the correct network was selected, the issue may be local to the wallet, its network connection, or its service provider. Avoid repeatedly sending the same payment until you understand whether the first attempt was actually broadcast.<\/p>\n
Networks have limited processing capacity. When demand rises, many valid transactions may compete for available block space. Fee rules vary, but transactions offering fee conditions that are unattractive under current conditions can remain pending longer than expected. A wallet\u2019s time estimate is not a guarantee.<\/p>\n
Some wallets offer speed-up or replacement functions on compatible networks. These tools create a related transaction under specific protocol rules; they do not edit a transaction that is already confirmed. Using custom replacement settings without understanding the nonce and fee rules can make the situation more confusing, so follow the documentation for the wallet and network involved. MetaMask\u2019s official guidance, for example, notes that cancellation can only be attempted while a transaction remains pending. [5]<\/a><\/sup><\/p>\n On networks that process transactions from an address in sequence, a later transfer may wait behind an older pending transaction. The later transaction may have a reasonable fee and still remain unprocessed because the network expects the earlier sequence number first. An explorer may expose this sequence information as a nonce, although field names and presentation differ.<\/p>\n Inclusion in a block does not mean that every recipient will immediately release the funds. A platform can wait for additional blocks, protocol finality, or another network-specific threshold. The required level may vary by asset, network, deposit size, operational conditions, and the recipient\u2019s risk policy. There is no universal confirmation count that applies to every transfer.<\/p>\n If the explorer shows a successful transaction with sufficient confirmations, the delay may be outside the blockchain. A custodial platform still needs to detect the deposit, associate it with an account, apply its current confirmation policy, and complete any operational or compliance checks relevant to that transaction. Those checks depend on the direction of the operation and their results; current requirements should be reviewed before creating an exchange request.<\/p>\n A wrong or missing Memo or Tag can also prevent automatic account credit when a recipient explicitly requires one. The blockchain may show a successful transfer to the platform\u2019s address while the platform cannot determine which customer balance should receive it. Never invent a Memo or Tag: copy it only from the recipient\u2019s current deposit instructions.<\/p>\n A wallet is an interface to blockchain data, not the blockchain itself. Temporary synchronization, indexing, or connectivity problems can leave its displayed status behind the network record. Cross-check the TXID in a suitable explorer and verify that the network and addresses match before taking further action.<\/p>\n Asset<\/strong> means what you are sending; network<\/strong> means the blockchain route used to send it. The same token label may appear on more than one network. If the sender chooses a network that the recipient does not support for that deposit, waiting for additional confirmations will not solve the mismatch.<\/p>\n A coin<\/strong> is native to its blockchain, while a token<\/strong> relies on a host network. The practical consequence is fee funding: a wallet can hold a token yet lack the native coin required to pay the network fee needed to move it.<\/p>\n Gas<\/strong> measures computational work on compatible smart-contract networks. The transaction fee<\/strong> is the amount charged for network processing. Treating them as identical can lead to incorrect assumptions about why a transaction failed or how much native coin is required.<\/p>\n Pending<\/strong> normally means the transaction has not completed the required on-chain inclusion stage. Confirmed<\/strong> means it has entered the accepted blockchain history under the network\u2019s rules. A confirmed transfer generally cannot be cancelled through a normal wallet function.<\/p>\n Confirmed<\/strong> is a blockchain status. Credited<\/strong> is a recipient-service status. A transaction can be confirmed on-chain while an exchange is still applying its confirmation threshold, matching the deposit, performing checks, or updating the customer balance.<\/p>\n A TXID<\/strong> identifies an on-chain transaction and can be checked in a block explorer. An order ID<\/strong> belongs to a wallet provider, exchange, merchant, or other service. Entering an order ID into a blockchain explorer usually produces no result, while giving only a TXID to support may not identify the related exchange request.<\/p>\nAn earlier transaction is blocking a later one<\/h3>\n
The newest block has not reached the required confidence level<\/h3>\n
The network is finished, but the recipient is not<\/h3>\n
The wallet or explorer view is out of date<\/h3>\n
Do not confuse these pairs<\/h2>\n
Asset and network<\/h3>\n
Coin and token<\/h3>\n
Gas and transaction fee<\/h3>\n
Pending and confirmed<\/h3>\n
Confirmed and credited<\/h3>\n
TXID and exchange order ID<\/h3>\n
Network fee and exchange-rate effects<\/h3>\n