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.
e7c011780db274693a5f121a559eab55a141c218b7c5a17a110ccfdf1cb5fd44
Both payments are on their chains and locked to the same secret hash caa8df0b8262ffe37256859e9fc76cc72dbde11a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: e7c011780db274693a5f121a559eab55a141c218b7c5a17a110ccfdf1cb5fd44
- MakerPaymentSpent: dd1bb8c95d3334ff08e13007712a16f11c19ea01f0fdc122dfcc4b4cc3604a6c
20427d2f20365847e628910f5aa382f3fc406f65f485aaa91865dbf7ff94bc22
Both payments are on their chains and locked to the same secret hash caa8df0b8262ffe37256859e9fc76cc72dbde11a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 402f2b0143820df1bbc8a14b819d435c118b67e26051b4833991ef7e1e1a5803
- TakerPaymentSent · TakerPaymentReceived: 20427d2f20365847e628910f5aa382f3fc406f65f485aaa91865dbf7ff94bc22
- TakerPaymentSpent: 41e0935911e9244476da42aba77ad2403f555d6e719274477cb0b499dc6bf6d5
Reported by kdf-statsdb-8762.