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.
329a3b55ca09d933c30c6790b3890eeee73a8642bb5e170ba83db635711d53cf
Both payments are on their chains and locked to the same secret hash 2a0cf36db079aee232ff12923d0579dcc5244763, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 329a3b55ca09d933c30c6790b3890eeee73a8642bb5e170ba83db635711d53cf
- MakerPaymentSpent: e8007928155a8e7972892a3a8223800c907e5e9ebc38ff1619a410aff8eb3c31
4c2435518fc05757e80fb6877f6bf856ee102578b466f85e8f466df60d668a48
Both payments are on their chains and locked to the same secret hash 2a0cf36db079aee232ff12923d0579dcc5244763, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 612856e742babcba9aa499818c6d2c6e0e84cb0ac24a814351ea41cfd57fcc86
- TakerPaymentReceived · TakerPaymentSent: 4c2435518fc05757e80fb6877f6bf856ee102578b466f85e8f466df60d668a48
- TakerPaymentSpent: 4a4afc8dd31364893d370b09fd17e94dfd32098cfb6c599d2de48968c4bca3b5
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.