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.
a3c5eb13db4dcf67693dfb1bbdfaeec3e0dcc1cb7176da9c4bf13ca57fd20c05
Both payments are on their chains and locked to the same secret hash c7ba3986c9a2cd3b6754d4510fa48a7a00a5711e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a3c5eb13db4dcf67693dfb1bbdfaeec3e0dcc1cb7176da9c4bf13ca57fd20c05
- MakerPaymentSpent: f60150f7400226200d83feb5daf4150637eacdcceec3bcca633f6a6985acbd28
584385eae8f21d4911148f570068b1205efe4a6be816ac8d465f9802c2d06f03
Both payments are on their chains and locked to the same secret hash c7ba3986c9a2cd3b6754d4510fa48a7a00a5711e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cf8aa37f0de16bccda9a2b5aa76f64c3d2967d308765572da8c1c8595dd04e79
- TakerPaymentSent · TakerPaymentReceived: 584385eae8f21d4911148f570068b1205efe4a6be816ac8d465f9802c2d06f03
- TakerPaymentSpent: 3817967ffcc98218dabe6c82f333bae220d453700297ae4bc6e39f5f93e414d7
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.