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.
95fd7fb388111332485388421354bb50895a6611292b9bb2d77d45922b2d5826
Both payments are on their chains and locked to the same secret hash b4d17ceeef433f89b46d04eec5d8254a640c1192, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 95fd7fb388111332485388421354bb50895a6611292b9bb2d77d45922b2d5826
- MakerPaymentSpent: 973394cc95804f42fd7e67b1b5ece9a74d99bfceab97224ac879d3c44ee3d68f
3a55dada97b3bd755f80a26eef7ee170857822b6b7af398cdc37b8ac8d309be9
Both payments are on their chains and locked to the same secret hash b4d17ceeef433f89b46d04eec5d8254a640c1192, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ea3d7e3190c3b67ef01cd19e7331a95bc348a29737f577bdd359b4396f2b0953
- TakerPaymentSent · TakerPaymentReceived: 3a55dada97b3bd755f80a26eef7ee170857822b6b7af398cdc37b8ac8d309be9
- TakerPaymentSpent: ce69e2b497913cf104c50d2b0f9630feeb58414418ea6a81621868b09fec6b03
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.