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.
4b0059174cda1c2752cb9aea91f080b3f8e1ab77e7cf867d35e12374b6fd1f5c
Both payments are on their chains and locked to the same secret hash 352448ad4ebc9c285c65872c5cd8785ceabe0365, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4b0059174cda1c2752cb9aea91f080b3f8e1ab77e7cf867d35e12374b6fd1f5c
- MakerPaymentSpent: cf94490fbcaddf7cc88fdc54a3c7ee5fe020350dec470ee860dc4d76c6876aab
c99c67e51f9097a42b5e4e36e0111494061126d550817d7dd4fc60d685b0c9a7
Both payments are on their chains and locked to the same secret hash 352448ad4ebc9c285c65872c5cd8785ceabe0365, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1420b2617d74dc017ce7da6d74c194ab3b33fb3afb3c5a105c94aa4b31f3bb0a
- TakerPaymentSent · TakerPaymentReceived: c99c67e51f9097a42b5e4e36e0111494061126d550817d7dd4fc60d685b0c9a7
- TakerPaymentSpent: 994f6dabc7ddfba9aee21afd1d7155e3a26074de01abc86bd822ebd3df1f1a42
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.