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.
8d60a69e7e50e46bcaccca1d88f8f72a7d05cf7eb7606c180651f82f4faaba8d
Both payments are on their chains and locked to the same secret hash bb0cc8fdb9018f49895280d1d6a9c2698fe12014, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 8d60a69e7e50e46bcaccca1d88f8f72a7d05cf7eb7606c180651f82f4faaba8d
af8ee4b6fd59d5bc20cb0d4dc9cb400c56c6275a7ba28a77077391d49324bc7a
Both payments are on their chains and locked to the same secret hash bb0cc8fdb9018f49895280d1d6a9c2698fe12014, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 60f5a451c3a706209de16db887222c8c6c3f7c7055f8a581d636073683e4ce33
- TakerPaymentReceived: af8ee4b6fd59d5bc20cb0d4dc9cb400c56c6275a7ba28a77077391d49324bc7a
- TakerPaymentSpent: 9eb34a7a436f0986487b2868e0579a7bc655e9f3968ab583af15d463680e487d
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.