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.
66791daf51e59216de14810116f001d7c6e87f3a3288301a0e595b5be8720434
Both payments are on their chains and locked to the same secret hash 7852befd908002f84f0fbb779cf13b3cb0a5f81a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 66791daf51e59216de14810116f001d7c6e87f3a3288301a0e595b5be8720434
- MakerPaymentSpent: 70fe822dae4c905013639c27a72a066f47d469dcb91ea5b1a16f8dac3a8772ad
cc2f7c5bcd33f25601757a8369c5d03f901650f05311701bc96de9dde4998763
Both payments are on their chains and locked to the same secret hash 7852befd908002f84f0fbb779cf13b3cb0a5f81a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4e530c969c8ee8ebe104f6748c55e03d65853de1f9fdae286c0ee5760ec5bc76
- TakerPaymentSent · TakerPaymentReceived: cc2f7c5bcd33f25601757a8369c5d03f901650f05311701bc96de9dde4998763
- TakerPaymentSpent: 79821c4fc07bfb0210fd65d011240afe7a8383b377141b98b3910e1af4fb9eec
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.