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.
9ea084e66b7e9883dea9fd6f11ddcc73b03a0a67216d2aa0549073cd46162eaf
Both payments are on their chains and locked to the same secret hash d589ba070b9cccc95fbbd530cccc47debd73adf8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9ea084e66b7e9883dea9fd6f11ddcc73b03a0a67216d2aa0549073cd46162eaf
- MakerPaymentSpent: 39765ae1340268396d10a2d0a1026f365b3458bfff34872c57887e6be95001c2
72d5d387b257f09a1b9e7897f0cb4bd5136b69795a20e496eb1714878d8674a5
Both payments are on their chains and locked to the same secret hash d589ba070b9cccc95fbbd530cccc47debd73adf8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0eb328511f4b87a59be1f03a03796e12ed7a12729e0f4ec28fae653d8a53a2c6
- TakerPaymentSent · TakerPaymentReceived: 72d5d387b257f09a1b9e7897f0cb4bd5136b69795a20e496eb1714878d8674a5
- TakerPaymentSpent: 0407e8de337435b04ad4504d0dc279fde1346dd77baeb7991168650e74ad52a9
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.