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.
64b8f958919525fa81a6b031bbcf114fc337db80fbe7f65a8c8f8caa3ba81f54
Both payments are on their chains and locked to the same secret hash ad372210e1ca637927688d9cf78c99168c8543f5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 64b8f958919525fa81a6b031bbcf114fc337db80fbe7f65a8c8f8caa3ba81f54
- MakerPaymentSpent: 89fe0cefcca542bd55e0a854bbb50abe64c92aff50237a17a67d42d9e58e7aa0
1504b2cd3e008e810574cbaec438f720f564d8537c9fdaa912854f3e7fde6426
Both payments are on their chains and locked to the same secret hash ad372210e1ca637927688d9cf78c99168c8543f5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 05cd9535ccafdde7eaa86752f1e467476b1e6f5ea55eeae4f1a6dd987592e4fb
- TakerPaymentReceived · TakerPaymentSent: 1504b2cd3e008e810574cbaec438f720f564d8537c9fdaa912854f3e7fde6426
- TakerPaymentSpent: 96a3bc7ce8dd0dfeb1c9cafb7aced837e42e766e601416c52cae870d8f06cefb
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.