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.
b015b3d699fd35eda5c245bcaf84ac8df994cdd2b369796260d76be2119e77a2
Both payments are on their chains and locked to the same secret hash a6e834fc0332000671e1d193379212467470983d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b015b3d699fd35eda5c245bcaf84ac8df994cdd2b369796260d76be2119e77a2
- MakerPaymentSpent: 6364138978c6bcc4a726dfc375dd3fd53408aba58b764aa383b6861afed5d6af
e7db3fa7362234b3bafef1839cef8a9b8a187a64cc82fe447e7c1bb00fd4eeab
Both payments are on their chains and locked to the same secret hash a6e834fc0332000671e1d193379212467470983d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fb4dfc1feeed05c1eb600de42bc82bbcbecd24fdb04094a191c2d772d989fa05
- TakerPaymentSent · TakerPaymentReceived: e7db3fa7362234b3bafef1839cef8a9b8a187a64cc82fe447e7c1bb00fd4eeab
- TakerPaymentSpent: df20fbb3e1496d3b671cd1d83631cc91a942c810aa4ee33f9d3ec7b34b85bf89
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.