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.
a086d0d58ac595eebe44fdf37fad1f08856aa16ea6a4a74a17c34824cd3d7087
Both payments are on their chains and locked to the same secret hash 249bf9d7774cd6a403ea451dff54971a20702ceb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a086d0d58ac595eebe44fdf37fad1f08856aa16ea6a4a74a17c34824cd3d7087
- MakerPaymentSpent: 043b2165bbcb849cc2c2ded8354606352f0b02bea1af7cfc735cea30890b9bfb
cc97df55f2baeb34d1988cea8911dd79578899dd201545c4a69154d62b2e9191
Both payments are on their chains and locked to the same secret hash 249bf9d7774cd6a403ea451dff54971a20702ceb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c0abb7cac03ecc3087685374dc16b83bd660ca7614116f9f4dcb3824a9b87099
- TakerPaymentSent · TakerPaymentReceived: cc97df55f2baeb34d1988cea8911dd79578899dd201545c4a69154d62b2e9191
- TakerPaymentSpent: b1fa7879bc945fa570053487f1d2ec13328a62f427020d968e5caf5a25ff4eb8
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.