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.
a26d266851273dc1797ccac5c1fc91978d59e87189edd0792142e8408ddc3ee7
Both payments are on their chains and locked to the same secret hash 55baab9b3e85898dde599766cb0dbfad535f6eb8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a26d266851273dc1797ccac5c1fc91978d59e87189edd0792142e8408ddc3ee7
- MakerPaymentSpent: 7187745b04acdd258752ef0419e7eaaa3a4c10ceac00a6440da8a520a810fa2a
77299b54d4613dff06ee2b140a9d67988f9b718a3f108d31031caf1238f1cec9
Both payments are on their chains and locked to the same secret hash 55baab9b3e85898dde599766cb0dbfad535f6eb8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 68dc5fc62f80f751c322ce4422786ff09789a72f6d68ba017e588611470d84b2
- TakerPaymentSent · TakerPaymentReceived: 77299b54d4613dff06ee2b140a9d67988f9b718a3f108d31031caf1238f1cec9
- TakerPaymentSpent: e740e88cec2222015a51e9fc0b1fe910473ab1cc727d057b92cbd67abde972b1
Reported by kdf-statsdb.