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.
080f0df7f857afe54c5e02cac412cd71282f6f78ec7f9938b4a1640430f3440d
Both payments are on their chains and locked to the same secret hash 0738c9955c354d544eff0c9b2893b94a1f9a2e44, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 080f0df7f857afe54c5e02cac412cd71282f6f78ec7f9938b4a1640430f3440d
- MakerPaymentSpent: 2f44eabdd7bbdd32b46e43c070d0cd7dfbf1ba6e4c7bf9d8ef4d306d89af0e37
75b61ad6d40b570ebe02e11ad92f3faac39245d4d11834a49bdfacbe2895b73c
Both payments are on their chains and locked to the same secret hash 0738c9955c354d544eff0c9b2893b94a1f9a2e44, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9c30833f20902c3e932731e9d561cdd987f6c1e2e1d41302babce8d98d967774
- TakerPaymentSent · TakerPaymentReceived: 75b61ad6d40b570ebe02e11ad92f3faac39245d4d11834a49bdfacbe2895b73c
- TakerPaymentSpent: 4f5719361e16c501f3f950c28eb2ac8e691179b1841c9547b7278ea1856a13bc
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.