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.
add0d50253aad4664d75e7cef9abfb2ae12ac8eaf3cbbd44354a3307ed6b34cf
Both payments are on their chains and locked to the same secret hash de2bb0138cadd89d91d42b3c4119e84f59745e9b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: add0d50253aad4664d75e7cef9abfb2ae12ac8eaf3cbbd44354a3307ed6b34cf
- MakerPaymentSpent: 0b892cc278d8b448f0b82a1872704599be7e9589dcdf1198c6abd9cfbeaffec2
0152e8a8c528bb12853c43e1bfc44dc30e6313bcc30f0f8454f6a402910355be
Both payments are on their chains and locked to the same secret hash de2bb0138cadd89d91d42b3c4119e84f59745e9b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d3bcd786d0ac30d81a3b1d87f20a11e8740c5c7114f9c6e84b2a724a6b6f84a1
- TakerPaymentSent · TakerPaymentReceived: 0152e8a8c528bb12853c43e1bfc44dc30e6313bcc30f0f8454f6a402910355be
- TakerPaymentSpent: ba4d68e20c28e127bdf5f1634dcf94c679fdd8d513d748b0c00bdc5df9b231d6
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.