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.
412cfe556fd180dc7eb71bc4254e078b3f2d3b3c7fb07c8c4d0e3f797ab10103
Both payments are on their chains and locked to the same secret hash 61a5af92a750f5691e972db4c34c3ebe6e5551e1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 412cfe556fd180dc7eb71bc4254e078b3f2d3b3c7fb07c8c4d0e3f797ab10103
- MakerPaymentSpent: 391e24c3800b188f41ad5632390c5847ae55c009112b98cc0d2f83221da011a2
22c9d927a74f4006af36d932fb905024653735be76c5b09b945df6adf457e64f
Both payments are on their chains and locked to the same secret hash 61a5af92a750f5691e972db4c34c3ebe6e5551e1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2183e671f73e6d994548e5122a4e8559e1f856613e0b7edf2a9d1a2c7192b924
- TakerPaymentSent · TakerPaymentReceived: 22c9d927a74f4006af36d932fb905024653735be76c5b09b945df6adf457e64f
- TakerPaymentSpent: a9bfba9b5b3a283377137927c07b3aad657f97d6b5d3c77003867cb5562d1d7d
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.