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.
b441d36a3999d89dda0e00f21a58d1e84aa733cf7e24156a5173206a54a77bd6
Both payments are on their chains and locked to the same secret hash 936f2506f423d94283a16ec4975f024e02bea22c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b441d36a3999d89dda0e00f21a58d1e84aa733cf7e24156a5173206a54a77bd6
- MakerPaymentSpent: 08dcc397115c9124c4a13eb704fac2f322b91ffeddd6baa19a3e26ddf37c2e6f
295bd5db828fccb1645656eea34badd3bead4027efe865e75b476bdb9210c10d
Both payments are on their chains and locked to the same secret hash 936f2506f423d94283a16ec4975f024e02bea22c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 688865f395ba6a015cb3070b0ffff58feea2187070a1c05d2879746849c8e272
- TakerPaymentSent · TakerPaymentReceived: 295bd5db828fccb1645656eea34badd3bead4027efe865e75b476bdb9210c10d
- TakerPaymentSpent: 2af0c014cea56663f45b364839836a5e6a9aa90b2042d55e245776675c284f95
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.