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.
1828fe96f24a49b8bd348eeac49fb0ee67f2b4f2c8d76dc50684d740501cbb9d
Both payments are on their chains and locked to the same secret hash 85a35cc146d4ce09fa33f60a75baaf98f15fd7f7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1828fe96f24a49b8bd348eeac49fb0ee67f2b4f2c8d76dc50684d740501cbb9d
- MakerPaymentSpent: 0d7664f7449d24a459d45f45368f2465bec3ae48661a84d445e8035f64c83ec8
0d956cbbae8a7d67fb91b60ac56b8b71deff76ed355d0d2115557399020502ce
Both payments are on their chains and locked to the same secret hash 85a35cc146d4ce09fa33f60a75baaf98f15fd7f7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: b0e443084dd8e70466e08e3a5015a731011643cccd1137cc019679c812013082
- TakerPaymentReceived · TakerPaymentSent: 0d956cbbae8a7d67fb91b60ac56b8b71deff76ed355d0d2115557399020502ce
- TakerPaymentSpent: dc9c87abf5df3295775be117e289ca97f0dde54c7c4eb1bf1fffeb7ffcc8ba17
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.