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.
7b3529557a575c154146b8fa106cc26bbab224c2ee777c2ede4d3a0bd0626c28
Both payments are on their chains and locked to the same secret hash 86ebf55fece393550c349cd8167c8588edf68920, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7b3529557a575c154146b8fa106cc26bbab224c2ee777c2ede4d3a0bd0626c28
- MakerPaymentSpent: 390f715752d5b52dd263450a8e222fbdcd08a6d4a9bdd7f665efd16a6db6e252
15bea10a326aeb2b2141b83852f965f9d2a294852b6baeb1f032e64c241cf00c
Both payments are on their chains and locked to the same secret hash 86ebf55fece393550c349cd8167c8588edf68920, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2723b0284a98b23332a8383ae135e6342ca56f46d2853c4146ef4665f91f9c6c
- TakerPaymentSent · TakerPaymentReceived: 15bea10a326aeb2b2141b83852f965f9d2a294852b6baeb1f032e64c241cf00c
- TakerPaymentSpent: 0986c5d841e59fb080cfdeaa686bae11038c541928be90a9b7f38b513b845a4b
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.