> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/mayan-bridge-track-swaps-without-rechecking-every-chain.md). # Mayan Bridge: Track Swaps Without Rechecking Every Chain Swap tracking means following one source transaction until the destination token reaches its wallet. The key condition is that a confirmed payment can still be moving between chains. Save the source transaction hash as soon as you submit. It is the transaction’s unique ID, and the explorer uses it to find the swap; knowing [how to choose a Mayan bridge route](https://dune.com/polly_defi/first-time-mayan-bridge-how-to-choose-a-route) also helps you know which source and destination details to check. Keep the hash until the swap finishes. ### One source hash follows the whole swap A Mayan bridge swap starts when your wallet submits a transaction on the source chain, the network where your tokens begin. After that transaction is confirmed, the bridge processes the cross-chain transfer and swap, then sends the output token to the destination wallet. That middle step is why checking only the source chain can mislead you. A source transaction marked “confirmed” means your payment reached the chain; it does not prove the destination token has arrived. Search the source hash in Mayan Explorer to see the overall status and destination details. For example, say you swap 250 USDC from Arbitrum to Solana. Search the Arbitrum transaction hash, then check the listed destination chain, wallet, token, and amount. You do not need to search separately for a matching Solana transaction unless the swap finishes and you want to confirm the deposit directly. ### Read the status before taking another step “In progress” means the swap has not reached a final state, so keep checking the same record. The source payment may be confirmed while the cross-chain work is still underway; avoid sending the swap again, since that could create a second transfer. “Completed” means the swap finished. Check the destination wallet and token shown in the record, then look for the deposit in that wallet. If it does not appear, verify that you are viewing the right network and token; wallets may hide tokens until you add them. “Refunded” means the input was returned on the source chain. Check that wallet’s activity and token balance before retrying. A refund is not the same as a completed destination transfer, so searching only the destination chain will not show where the funds went. ### Check less often, but keep the right record For regular swaps, bookmark the explorer and paste in the source hash once. Refresh the record after a short wait instead of repeatedly checking both block explorers. Mayan’s tracking API, a web service that reports swap details, uses the same source hash and returns three useful states: *INPROGRESS*, *COMPLETED*, and *REFUNDED*. If a swap remains in progress, give it time and check the record again. Cross-chain steps take different amounts of time, so a fixed wait is not a reliable failure test. If you contact the service or app you used, include the source hash, source chain, destination chain, and current status. Never share your recovery phrase or private key to get help. ### Confirm the destination before you move on Once complete, compare the recorded destination address with the wallet you intended to use. Then confirm the token and received amount; the output can differ from the input because the swap changes tokens and fees may apply. Save the explorer record if you reconcile trades or need to follow up later. For a fast repeatable check, use the same short sequence each time: * Copy the source transaction hash after submission. * Search it in the explorer and read the current status. * For “in progress,” wait and check that same record again. * For “completed,” verify the destination wallet, token, and amount. * For “refunded,” confirm the return on the source chain before retrying. #### What if the source transaction is confirmed but the swap is still in progress? Keep tracking the original source hash. Confirmation means the source chain accepted your payment, while the cross-chain transfer may still be underway. Check the explorer again later. Do not submit a duplicate swap while the first record remains in progress. #### Should I search by wallet address or transaction hash? Use the source transaction hash first because it identifies the specific swap. Searching by wallet address can show many transfers and make it harder to find the right one. Keep the hash until the destination deposit is confirmed or the source refund appears. #### What details should I check after completion? Check the destination chain, wallet address, token, and received amount in the explorer. Then confirm the token appears in the intended wallet on that network. If it is missing, check whether the wallet hides that token by default before assuming the transfer failed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://aboutcryptotalks.gitbook.io/aboutcrypto/mayan-bridge-track-swaps-without-rechecking-every-chain.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.