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.
17004a8d669b2d1ee38168ad3025767826e26815e965169967b0a757770da086
Both payments are on their chains and locked to the same secret hash f2b6a9541c868340dbe9b3406918c51af827429d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 17004a8d669b2d1ee38168ad3025767826e26815e965169967b0a757770da086
- MakerPaymentSpent: cbd4ab5027ff00cccd527ebf8ac3e8e08edd52e97a00aaa0051862cb03270ecc
2865add13fb593bc1bfcf575c120ebe6f3dd316966cdaa1216c4a7134268afc0
Both payments are on their chains and locked to the same secret hash f2b6a9541c868340dbe9b3406918c51af827429d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8903387cf2b59dbc3c2b808660baa03d8785083ba9afa15af844af4850547bc5
- TakerPaymentSent · TakerPaymentReceived: 2865add13fb593bc1bfcf575c120ebe6f3dd316966cdaa1216c4a7134268afc0
- TakerPaymentSpent: be06e030f6f9c03e21cdb37488040f3656ac1fa858b45b4af3985c1c5da1de2b
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.