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.
685be54ee9ddcdee9316356bbf837e2a90c1a17af5e83f61ef3f7120eab32f2c
Both payments are on their chains and locked to the same secret hash 8ad5bb468e621a9d39590965baca6777bb16b31c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 685be54ee9ddcdee9316356bbf837e2a90c1a17af5e83f61ef3f7120eab32f2c
- MakerPaymentSpent: 1df01b8145b24f5b26b1f63b3de44d3dfbbe174a094ff589c5fce27af815b7e4
ddaf321c865c6ec4471adcf11a103c466305c333bd88a1c0841400cedb69b211
Both payments are on their chains and locked to the same secret hash 8ad5bb468e621a9d39590965baca6777bb16b31c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 693b36e463b728523c4c9c34ac772aa39ead0ad2616461d89240d9ec22c590a5
- TakerPaymentSent · TakerPaymentReceived: ddaf321c865c6ec4471adcf11a103c466305c333bd88a1c0841400cedb69b211
- TakerPaymentSpent: 1ab72e906b2e7e1a13a26dd6802baab71f555f0b4f5653166041be3bf9fc1fc2
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.