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.
2856fb070031a948558e35438d72367df77388e3167028f07b8f51d24cea2be3
Both payments are on their chains and locked to the same secret hash 82318273caae32f4e3f1f6c96378bcc029f9327a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2856fb070031a948558e35438d72367df77388e3167028f07b8f51d24cea2be3
- MakerPaymentSpent: 114eeaa6adb872a4f6333be9576dea9fa182962ab1c2c3efdc1da5e16fcdc7fa
258a4e5194ceb305ab1cc1655f02154c64d33266223cd34d9d19927e719308ad
Both payments are on their chains and locked to the same secret hash 82318273caae32f4e3f1f6c96378bcc029f9327a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e36d0428c74e3f030736cded528310d5b51fd3df3008730a12634f648d6ffba9
- TakerPaymentSent · TakerPaymentReceived: 258a4e5194ceb305ab1cc1655f02154c64d33266223cd34d9d19927e719308ad
- TakerPaymentSpent: 95df3eb1d68f0d917e20ed9a129546c1540febf8aaafd439cd41800a0cb44307
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.