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.
7271beccd5f53a4a8eb0a6c733ca3d30fa1e1203da91b6e1c87e65e6fd56a4aa
Both payments are on their chains and locked to the same secret hash ea45c24ca53d5e47027458138b45c407092f6a94, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7271beccd5f53a4a8eb0a6c733ca3d30fa1e1203da91b6e1c87e65e6fd56a4aa
- MakerPaymentSpent: a12ecd510118431489323efa1e6b09c8e36f696cdbc9f8e90dc5542ba71868d6
abf671f19814d3f8a9a676982577f9721e61542fbc9d1cd09ca280f4a1f2cc43
Both payments are on their chains and locked to the same secret hash ea45c24ca53d5e47027458138b45c407092f6a94, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d26d14e04c589c51fb7e3b4e411a2629b141218914e456702c4660b882ea86d3
- TakerPaymentSent · TakerPaymentReceived: abf671f19814d3f8a9a676982577f9721e61542fbc9d1cd09ca280f4a1f2cc43
- TakerPaymentSpent: 25479cdfa21b6f08d81a2f065359da66d6a7f6fec4aa67db365a2fdbcef8646b
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.