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.
f935e977fefe7ef9cb3e7a0fd8cfbd6d669039956a314b8cae47f27aa2533b1f
Both payments are on their chains and locked to the same secret hash 1220ae9e8e5264fc673674f40508114035f60a9c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f935e977fefe7ef9cb3e7a0fd8cfbd6d669039956a314b8cae47f27aa2533b1f
- MakerPaymentSpent: 39560119e28a99e7636b85cdfa0106050b90758edfec9565985ef56ff04ec3fc
ab5cf48cb8d0aab95cda1479513877eecf4e8043aeca571ab1264ad0c43684ad
Both payments are on their chains and locked to the same secret hash 1220ae9e8e5264fc673674f40508114035f60a9c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58bc887d45fbd00878be60649cf2c81637b6173955dfe36ce3ebde5ce4e1df38
- TakerPaymentSent · TakerPaymentReceived: ab5cf48cb8d0aab95cda1479513877eecf4e8043aeca571ab1264ad0c43684ad
- TakerPaymentSpent: 55ed10ee17d2a5e01b8faa3e3fc58095a8f110d5da86810603e8413e5e154ba1
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.