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.
b69bd5a38f83d7b4dd6a6177484e77b3a9a9d87a124568752f0ce330996cb70b
Both payments are on their chains and locked to the same secret hash ffb4ba0bdc45cf8168bc6d61757999660105ae35, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b69bd5a38f83d7b4dd6a6177484e77b3a9a9d87a124568752f0ce330996cb70b
- MakerPaymentSpent: bd5923924ad8e94501c3b2168c7e772eda572465af8f3e422094fd84980b8cdf
973db5825d79dda1bff83f324f7d8db0f4b1060d5e8c815501dee3fd2dc8b811
Both payments are on their chains and locked to the same secret hash ffb4ba0bdc45cf8168bc6d61757999660105ae35, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 30b9a4e3462fb9eb3d1dcf269c905a26d089018b88bb8f73c931d1ad24ab9f21
- TakerPaymentSent · TakerPaymentReceived: 973db5825d79dda1bff83f324f7d8db0f4b1060d5e8c815501dee3fd2dc8b811
- TakerPaymentSpent: 10f3e0e903a077173bc4bac867e553981eb037191f2cf5c97eff6a94af2fdf64
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.