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.
40f6a42a7f26010900f9048df533760163c86a349a23d4deff2f894e64468647
Both payments are on their chains and locked to the same secret hash 8610c792f04a6f36f4453c6ef8432e869e3be44c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 40f6a42a7f26010900f9048df533760163c86a349a23d4deff2f894e64468647
- MakerPaymentSpent: cf8b33e8ea8eafb46998e4c7617290394e45c239c3560bf3bce15fa96cbac4a6
288fa01152be2c8b883517ff2678399cd4124a61846178fe92d3f6e27895ba99
Both payments are on their chains and locked to the same secret hash 8610c792f04a6f36f4453c6ef8432e869e3be44c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5410d9d48ab4a0f0d77fc2c370c94e140b323f05d4b9be3ddae8a0b42937c302
- TakerPaymentSent · TakerPaymentReceived: 288fa01152be2c8b883517ff2678399cd4124a61846178fe92d3f6e27895ba99
- TakerPaymentSpent: 6a2850f7304e1a3edf45cbf6564e0d8849ce346f3b184477d79d1a95bf41f85e
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.