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.
2b9874bbdbbb3bb2c9e773d5c62354cdeaad7b2a0b7fd6540fb391a6d9681325
Both payments are on their chains and locked to the same secret hash a5019eba631f16ddc26e18eec4e016a2b306454a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2b9874bbdbbb3bb2c9e773d5c62354cdeaad7b2a0b7fd6540fb391a6d9681325
- MakerPaymentSpent: 634315ff0c8f11d0ab603a940f6201d52c14e884137e39cf19aafc339bdb1112
d2b69a51d3d123b293d5c6b5b59c07acf09e3d200c3d4d0519204472cbbc1ff6
Both payments are on their chains and locked to the same secret hash a5019eba631f16ddc26e18eec4e016a2b306454a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 46ab268fea307dfcec8466e190ea0866562e879e7dca7f54cbcee2c591f564a7
- TakerPaymentSent · TakerPaymentReceived: d2b69a51d3d123b293d5c6b5b59c07acf09e3d200c3d4d0519204472cbbc1ff6
- TakerPaymentSpent: 5d8a9881dd15b545d05e7ecf05cafb15f4889704bb8a7b66983a3deb6a9d51d3
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.