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.
0ffb8873c94473cf84dc1fab78301d703b35d399fe5225242b01cbb8383f9339
Both payments are on their chains and locked to the same secret hash 22c4dbf59292df67b7ccb1a8bc89f7f9ef48353d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 0ffb8873c94473cf84dc1fab78301d703b35d399fe5225242b01cbb8383f9339
e42353f7b93077ef9e49a0021cd444027e715233f7a34791def4f9b858297ac6
Both payments are on their chains and locked to the same secret hash 22c4dbf59292df67b7ccb1a8bc89f7f9ef48353d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 121720d701c7f5f40c75a387b27a2e553cb3367fab81212c51dd77935b50d2b1
- TakerPaymentReceived: e42353f7b93077ef9e49a0021cd444027e715233f7a34791def4f9b858297ac6
- TakerPaymentSpent: f7ffeccf1ff33ed7cfa79cc3bac7f10a744a05b3d0d69a349bdd9a7db6668c76
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.