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.
342891ee9daf18c73086391ec9da37880cccc0c611144305a67ff58a92293dad
Both payments are on their chains and locked to the same secret hash 04c441d5fe099a59fc5992dee19dd453b56b49ce, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 342891ee9daf18c73086391ec9da37880cccc0c611144305a67ff58a92293dad
- MakerPaymentSpent: 6d3ebe6db8f215730cc96a8a53c63acde44dd15a20d2f2fbfd7bbc30e85dcaa3
62a66edcf3cea210055a7be0574a3ec34f8199df2f5aaadea100c0fbd666778f
Both payments are on their chains and locked to the same secret hash 04c441d5fe099a59fc5992dee19dd453b56b49ce, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 871b4fc5cc3870857d08298f7dff15abcb2b0c581ed5fffef84bdb0d29276baa
- TakerPaymentSent · TakerPaymentReceived: 62a66edcf3cea210055a7be0574a3ec34f8199df2f5aaadea100c0fbd666778f
- TakerPaymentSpent: c343c931ef090a48f6bc86a8bfdb2518340de4f68e379051912eb87b945ebffc
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.