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.
7f5a9d328823a1eff7d4fce57dbcf240d0d8e5c3e0f2d1c555d397296d6e2758
Both payments are on their chains and locked to the same secret hash 50e60a04f4f05a0c7e79192dd1a7beb317edca96, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7f5a9d328823a1eff7d4fce57dbcf240d0d8e5c3e0f2d1c555d397296d6e2758
- MakerPaymentSpent: 391af5df57d03b1c5ce9584d4a4c5de2eaaa63545f8e3ee987ecb32c43acadd8
91a371c196b8e3257090028df6feee92b1097e5bc49146edd7eddf385409df6d
Both payments are on their chains and locked to the same secret hash 50e60a04f4f05a0c7e79192dd1a7beb317edca96, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f96f6caf885db9bd0111ada2a9f7bbf275f7a3e2efd89b6ed599e278fe6e96e5
- TakerPaymentSent · TakerPaymentReceived: 91a371c196b8e3257090028df6feee92b1097e5bc49146edd7eddf385409df6d
- TakerPaymentSpent: 18cc1b4588dd6f80b9db548dfe32205c4c3b84610ebf600b9deed26f000eaf41
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.