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.
1f0ee8ec1da9468a29b057de5008953e977e8e4f0e659eb4860829cbb1d0b1d8
Both payments are on their chains and locked to the same secret hash c68c64d0f97e15f2776130dcc604b2e4c30b61ab, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1f0ee8ec1da9468a29b057de5008953e977e8e4f0e659eb4860829cbb1d0b1d8
- MakerPaymentSpent: e10ab35637bd46a68037b1bfef87eff8801dfb57550bb3b378d781d27c99e0fd
ac9379b39e9297ae459690c5353546092c256b103ea0bb5476f393895c435703
Both payments are on their chains and locked to the same secret hash c68c64d0f97e15f2776130dcc604b2e4c30b61ab, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: db2345abb0e98e860c1ef638119f290378170d52950157bcacdcf4a52d5877a6
- TakerPaymentSent · TakerPaymentReceived: ac9379b39e9297ae459690c5353546092c256b103ea0bb5476f393895c435703
- TakerPaymentSpent: e2e663721af05f1b2a8cdb87767833ca5e7f66b1f300a749119b6e282acdf1e1
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.