A cross-chain swap finishes after both networks and the transfer route settle. The time depends on how quickly the first chain confirms your payment, how the route processes it, and when the destination chain records the swapped asset. A same-chain swap waits on one network; Mayan Bridge swaps move and swap across chains, so the first confirmation is only part of the wait.
What determines how long a swap takes?
Three stages set the clock: source confirmation, route processing, and destination confirmation. A confirmation means a network has added your transaction to its record. Finality means the record is settled enough that the network is unlikely to undo it.
The source chain matters because networks confirm transactions at different speeds. For a concrete reference, Ethereum’s public block data shows slots of about 12 seconds and epochs of 32 slots. Under normal conditions, finality takes roughly two epochs, or about 13 minutes; a route that waits for finality may therefore spend that long on this stage alone.
Next, the bridge route verifies the source payment and arranges the destination transfer or swap. A bridge is software that coordinates a move between networks. Routes handle this stage differently, so a quick source confirmation does not guarantee a quick arrival.
The destination chain then records the result. A busy network, a slow route, or a temporary interruption can extend the wait. Mayan Bridge is an example of a service for coordinating a cross-chain move and swap; its completion time depends on the route and networks involved.
How can you estimate your own wait?
Build the estimate from the slowest parts of the route, rather than assuming one network’s speed applies to the whole trip. Before sending, identify the source and destination networks and check whether the quote or route information gives an expected completion time.
- Write down both networks. The source is where your crypto starts; the destination is where you expect to receive the swapped asset.
- Check source confirmation speed. Look up recent transactions on that network’s public block explorer, a website that shows recorded activity. Compare several recent transfers, since one unusually fast block can mislead.
- Allow for route processing. Treat the route’s stated estimate as separate from the source-chain time unless it clearly includes that stage.
- Check destination activity. If the route provides a transaction hash—a unique transaction ID—search it on the destination network’s block explorer to see whether the transfer has been recorded.
- Compare the stages. Add the expected source, route, and destination waits, then leave room for congestion or delays.
For example, if a route waits for Ethereum finality, allow around 13 minutes for that stage under normal conditions, then add the route’s processing time and destination confirmation. If the source is already confirmed but no destination record appears, the remaining wait is likely in route processing or destination settlement.
When should you investigate a delay?
Investigate when the route’s stated estimate has passed and the source transaction is confirmed, but there is still no destination result. First check the source transaction on its block explorer; if it failed or never confirmed, the route may not have received the payment.
If the source transaction succeeded, use its transaction hash to check any route status information available to you, then check the destination network for a record. A delay alone does not prove that funds are lost, but a confirmed source transaction with no expected destination result beyond the estimate is a reason to seek help through the service’s official channel.
For your next transfer, note the route estimate and save the source transaction hash before you send; both make a delay much easier to assess.
Top comments (0)