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.
d702a52f246a67f9172e16e23e4265bb1ece262c68be054d9f00e9dc115480d0
Both payments are on their chains and locked to the same secret hash 38738e4f8b7d2d64dec9fe9b56db991ddeb7555f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d702a52f246a67f9172e16e23e4265bb1ece262c68be054d9f00e9dc115480d0
- MakerPaymentSpent: 82a3ec6229c6972777a7110d91b952aaf7781058fd7f4fc66ae2ebe2137be892
94ce1d0108f6d6dbf2f68c6bdfb414a8e8a3291e86c5558846a72d871726c5c2
Both payments are on their chains and locked to the same secret hash 38738e4f8b7d2d64dec9fe9b56db991ddeb7555f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2363dd6a90d275608fd0f77a0ccc0d1f2fd0eb79b2df94361923872f7f03c303
- TakerPaymentSent · TakerPaymentReceived: 94ce1d0108f6d6dbf2f68c6bdfb414a8e8a3291e86c5558846a72d871726c5c2
- TakerPaymentSpent: 63613270938e8ee1f830f5b81e49ad58997383915cd4ff4f506a730956914af8
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.