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.
9bb5b8f37d24184e77249d4c9f5eeab92b8757b48a4d7a6c59701aa52ddc977a
Both payments are on their chains and locked to the same secret hash daf0b6e6d085a7f1c8ea39bc7711c1f6f03f37d4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9bb5b8f37d24184e77249d4c9f5eeab92b8757b48a4d7a6c59701aa52ddc977a
- MakerPaymentSpent: a08978212e56e3f1bafb9391ed9f32480e483a8f7f0765156103332a16437a4e
a039567d02f73809d99d54a1420060fe25a7fa0966a21a1154bf9d8e3ea92aff
Both payments are on their chains and locked to the same secret hash daf0b6e6d085a7f1c8ea39bc7711c1f6f03f37d4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 387633779946dd9823d72002686dbfcc9b6699d1a8fe4db15294e30359e53fc5
- TakerPaymentSent · TakerPaymentReceived: a039567d02f73809d99d54a1420060fe25a7fa0966a21a1154bf9d8e3ea92aff
- TakerPaymentSpent: 46fc8f3317a0d07572f73d40a7da2104016380c1daf8bb71b35e07757696be0a
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.