An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
063abb84855923775c0e0ac7e3fc84bccd568eb8d80cd394a46cd55c023355cf
Both payments are on their chains and locked to the same secret hash 0dc6b71f52dffc92e15875c3245e43cd612b5cde, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 063abb84855923775c0e0ac7e3fc84bccd568eb8d80cd394a46cd55c023355cf
- MakerPaymentSpent: 977bbb2c8968ba16deb5dce3938df9d57b713d2cc578f062e8670d307777b952
ba8e62c89419dc4405980743896ea546626b83840bf0fb54e77c3ee7c4e20cac
Both payments are on their chains and locked to the same secret hash 0dc6b71f52dffc92e15875c3245e43cd612b5cde, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fa0e921f385fc5327e27c2785b661e9a498ee16d442edbad687579c8fc5e3da8
- TakerPaymentSent · TakerPaymentReceived: ba8e62c89419dc4405980743896ea546626b83840bf0fb54e77c3ee7c4e20cac
- TakerPaymentSpent: 886986af2b90cf2ca15d610260f0c75794ec8615b9ac7845572a073cf7794b74
Reported by kdf-statsdb-8762.