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.
6bb21d74dba3be1fee61b04347dd8d5fc0a4919506bd92af86a4686adb2b04d3
Both payments are on their chains and locked to the same secret hash 528f7d42786e1535dd53aa5eb03c70c4110ebf15, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6bb21d74dba3be1fee61b04347dd8d5fc0a4919506bd92af86a4686adb2b04d3
- MakerPaymentSpent: 17964cec77c59b1c9d29066386adca72e743c262b2893ed5c57f5abfad0c3774
d9c43a029d212457d662f49d40c3bdf2101189ecaceccf9687d3161134d130e4
Both payments are on their chains and locked to the same secret hash 528f7d42786e1535dd53aa5eb03c70c4110ebf15, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b8617b294532b3018268696de681d9521c6fe3fb702334f40762d23217a028a2
- TakerPaymentSent · TakerPaymentReceived: d9c43a029d212457d662f49d40c3bdf2101189ecaceccf9687d3161134d130e4
- TakerPaymentSpent: 69c309f9688110a0b7b3f27ab3240d1bfdabf4156f028451a42c352ec1412649
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.