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.
78322312d93596851ff445daf8135bf86f31cca88e1c9384b0c14be82eb0ff49
Both payments are on their chains and locked to the same secret hash ca3cbfee2326f9c07913fb797bdb900292256821, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 78322312d93596851ff445daf8135bf86f31cca88e1c9384b0c14be82eb0ff49
- MakerPaymentSpent: 386827dc6580916d2b7770d293ef0196bb88fedc54a22ff203df843c92d2ab6e
d6fd1c94e61d61fd885221d51a29348eb1674941f1220c1ce8501f43d17ed289
Both payments are on their chains and locked to the same secret hash ca3cbfee2326f9c07913fb797bdb900292256821, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e74f957030166da88f577eb453f7c0f31b13e0c9fb12a9c4b28b8d85c24beca2
- TakerPaymentSent · TakerPaymentReceived: d6fd1c94e61d61fd885221d51a29348eb1674941f1220c1ce8501f43d17ed289
- TakerPaymentSpent: 997cd188faf6091777a06faf785e3b91ee2b29daee1f8a25ee683a821995cdc3
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.