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.
4cb879b61a2b3cff5eab5ff1559f0c4b4f7a9b8d89e9726e0329590c07c3da32
Both payments are on their chains and locked to the same secret hash c0eda666c5b53babe33299be7a75a2417f697b4f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4cb879b61a2b3cff5eab5ff1559f0c4b4f7a9b8d89e9726e0329590c07c3da32
- MakerPaymentSpent: 4a42b6db63d223489e4d3c2916a8194b40552c251d9050d24bfacf1444c54149
646184ea54dd83af74330d9df5d5cb94dcef4498380b480db4fbf7ba53043348
Both payments are on their chains and locked to the same secret hash c0eda666c5b53babe33299be7a75a2417f697b4f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: eb320008dc4f0d05c857fa87cd7a8fc7f3d0399e592e318e110507ac0fbdc592
- TakerPaymentSent · TakerPaymentReceived: 646184ea54dd83af74330d9df5d5cb94dcef4498380b480db4fbf7ba53043348
- TakerPaymentSpent: df9023a79db9e6513d74e42806abda7db0e4d51054320fbb362dcb6b20188927
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.