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.
08ae1b8f55dd48a1fe9170fdb85135bb8629f182d36367eb848e1a0f0ba82adc
Both payments are on their chains and locked to the same secret hash 9fdcf7165e9b42b7584dbf0306802965d7971e9d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 08ae1b8f55dd48a1fe9170fdb85135bb8629f182d36367eb848e1a0f0ba82adc
- MakerPaymentSpent: eb54071c4cea6017d4689ea27fada6fa0d52dbf847cbd2b82a8928ff855d5ad9
dd9bf1b75cc779cbfb5aaf88e797dcbc93bd26499ef4b6e6d188e80f600bbcac
Both payments are on their chains and locked to the same secret hash 9fdcf7165e9b42b7584dbf0306802965d7971e9d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 729733d5a69c794bc03492e281015cd49a4520493ee4213c0985d8db6700d4e2
- TakerPaymentSent · TakerPaymentReceived: dd9bf1b75cc779cbfb5aaf88e797dcbc93bd26499ef4b6e6d188e80f600bbcac
- TakerPaymentSpent: d49fac35d761f211820d4952f789b559f9ea5970d147a816526d82494a95742c
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.