If your TeleSwap source transaction has been sent but the destination asset is unclear, matching the source transaction, request, and destination records will identify the last completed stage or verify delivery. Gather the source transaction ID, expected destination network, recipient address, and token contract. Open TeleSwap request history and search by transaction ID or address history. Keep the TeleSwap BTC bridge request ID beside the transaction hashes so you can follow your transfer across networks without confusing it with another wallet transaction.
What Has the Source Transaction Established?
The source explorer tells you whether the transaction was broadcast and whether its network included it. For a Bitcoin source transaction, a mempool entry establishes broadcast; confirmations establish inclusion in blocks. Note the transaction ID and confirmation state. If the source is another supported network, use that network’s explorer to check its transaction status.
Suppose you see your Bitcoin transaction in the mempool but cannot yet find its request. The last stage you can establish is broadcast. A recently broadcast transaction can appear in the explorer before the request index updates, so the missing request alone does not establish an unsuccessful transfer. Once the explorer shows confirmations, look again for the associated request. Source inclusion provides evidence for the next stage, but it does not establish that the destination asset was sent.
Request State and Detailed Status Describe Different Events
The request state shows where processing stands; its detailed status helps distinguish work still underway from unsuccessful execution. Read them together, then open any linked proof and destination transaction records. A submitted proof means Bitcoin transaction evidence reached that stage. It does not mean the requested token reached your destination address. Likewise, a completed request is a processing result that you should compare with the destination transaction rather than treat as a wallet balance.
Continue the example: the Bitcoin transaction gains confirmations, and the request now shows proof submitted, but it has no successful destination transaction. Your evidence has advanced from source inclusion to proof submission; delivery remains unverified. If the detailed status reports processing underway, record that stage as pending. If it reports unsuccessful execution, record that outcome and the associated transaction or request ID. The TeleSwap request state by itself may not give you that distinction.
Has the Destination Token Arrived?
The destination explorer can establish delivery by showing the expected token transfer to the expected recipient on the expected network. Follow the request’s linked destination transaction, if one exists, and inspect its result and token transfer event. Match the recipient address and token contract to what you intended. A successful transaction involving your address is insufficient if it transferred a different asset.
Also inspect the recipient’s token balance on the explorer. An absent token display in your wallet does not establish an absent on-chain balance; the wallet may simply lack that token in its display. A transfer event can show delivery even if the current balance later changed. If the records establish delivery, you have your answer. Otherwise, write down the last completed stage, request ID, source hash, any destination hash, and the relevant status for further investigation.