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.
c3778e2cea661217ac55bee752e834817d9c87d084574e131eabb6a788fdc0bc
Both payments are on their chains and locked to the same secret hash 3ac57ec9c92a6f37af3bea505e55332477cf7fcf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c3778e2cea661217ac55bee752e834817d9c87d084574e131eabb6a788fdc0bc
- MakerPaymentSpent: 598f8400c2895301e03ef3aad8b21ad41a0f6732f1a25c3f99f187f39e8352f1
292b5d71a75ba933f31896ce20e79ecbf0d569902d95dd4aed92711aebeaf235
Both payments are on their chains and locked to the same secret hash 3ac57ec9c92a6f37af3bea505e55332477cf7fcf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cd9b3a14dd583ebaff8d6004735d6a358107c292bfcac5be45717934128e28c5
- TakerPaymentSent · TakerPaymentReceived: 292b5d71a75ba933f31896ce20e79ecbf0d569902d95dd4aed92711aebeaf235
- TakerPaymentSpent: cd2b9c8f087326acfc1cbb9e7bc88c1ebb380ff22603c0717909156d212d2d9e
Reported by kdf-statsdb.