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.
666e16411e48bf067d5e2c428da14c1d382d37a7da01b3a3809b0ac25f2d0290
Both payments are on their chains and locked to the same secret hash 1ff685619d5670ad72b67f7cc809483f799e5d05, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 666e16411e48bf067d5e2c428da14c1d382d37a7da01b3a3809b0ac25f2d0290
- MakerPaymentSpent: f20db344b243f2be45fe59c3c532692c1be6ab888f5cae4d02c85ef970f4dc0a
c00d5c67c53bfd716d89dadc1b22837b8734c84c419c074d52bf873d2f8eb919
Both payments are on their chains and locked to the same secret hash 1ff685619d5670ad72b67f7cc809483f799e5d05, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: fb826b0322572c9d5bce0fa947e67248bca063a8810b8f33f4b9893790d98994
- TakerPaymentSent · TakerPaymentReceived: c00d5c67c53bfd716d89dadc1b22837b8734c84c419c074d52bf873d2f8eb919
- TakerPaymentSpent: 813e9f0e618cf2374301f8e198f507d1476235080b42348f68666b6891bc5dc9
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.