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.
df989f577e8143c09f8277b10da84f7ebe8aa9942f4d66535b477877e1f4fd51
Both payments are on their chains and locked to the same secret hash f8d2e427a34f880c77098f0aec2eba117682eea6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: df989f577e8143c09f8277b10da84f7ebe8aa9942f4d66535b477877e1f4fd51
- MakerPaymentSpent: 95ef084ae8bab352cb6c5f32ea4ac46e53fe796ffa114d95fa545539a55a989a
ed56440714811f289f2671762475b22c1770e6c2e861934bcae6824f14020598
Both payments are on their chains and locked to the same secret hash f8d2e427a34f880c77098f0aec2eba117682eea6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d7d6a2be997769be69065a01acbf06e4483b84ba9fe03be18276560aac035077
- TakerPaymentSent · TakerPaymentReceived: ed56440714811f289f2671762475b22c1770e6c2e861934bcae6824f14020598
- TakerPaymentSpent: 9aa7cc238233b3a567e2f3ac832427d92367595ca18360542d628fa68125564f
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.