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.
6b375395b050078504cb5621559794454eda287d2f759d45cbd967ef968ce8ec
Both payments are on their chains and locked to the same secret hash c827dd24f00b2bf3407b1cd11fb5151eed8e5e7e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 6b375395b050078504cb5621559794454eda287d2f759d45cbd967ef968ce8ec
- MakerPaymentSpent: be25e513e1b17e39d9cd8daeb5bd16b36247229f81aaf9ed46945f3107ffae0d
d5f55884c89c406c458be2891955d4e7f5d6a31c20f5813bff1efead0eb94458
Both payments are on their chains and locked to the same secret hash c827dd24f00b2bf3407b1cd11fb5151eed8e5e7e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d885abd8439b84438eeb7fc57166217282fb460a739001f4d13b0154cadae4e2
- TakerPaymentSent · TakerPaymentReceived: d5f55884c89c406c458be2891955d4e7f5d6a31c20f5813bff1efead0eb94458
- TakerPaymentSpent: f552e6dd19c3374234aa8497a48c238cd8819b004e9083b59e357c30dce056ba
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.