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.
13745c4c0de07d71ffc01fe426f2cdafd80d19300de340d73c4d035407522905
Both payments are on their chains and locked to the same secret hash e0a2d36c275a179d78dc3032a5f6576e6611ec13, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 13745c4c0de07d71ffc01fe426f2cdafd80d19300de340d73c4d035407522905
- MakerPaymentSpent: 1a67bf990d4c562fe4404ad790dfc9061d5b8e91068e16ec83d2e727c2403309
d96578cfc8349e86b49bee1da8d83702e3725853516435e99aba443ca530a5ad
Both payments are on their chains and locked to the same secret hash e0a2d36c275a179d78dc3032a5f6576e6611ec13, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 515e9d8babc7a38eae222518a35dd8563607f25d5197498bdf336d3ce98e68c3
- TakerPaymentSent · TakerPaymentReceived: d96578cfc8349e86b49bee1da8d83702e3725853516435e99aba443ca530a5ad
- TakerPaymentSpent: 944ff665a6ae852f415028e5c536625d33085f99e7c814ca101d0dc6915cee34
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.