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.
9fe009fb31db49cb7ce3e22f596c8fa77f82f798fbcbfe9ea6afdfea70cb8489
Both payments are on their chains and locked to the same secret hash c3657805089b82dabcda983ed783f9cc825c417a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9fe009fb31db49cb7ce3e22f596c8fa77f82f798fbcbfe9ea6afdfea70cb8489
- MakerPaymentSpent: a66065c40113070eb9053bae194358c1314b2ccbcc06d61628cdbcbb82f63206
37a68bdbf8d23f394f0a22e1ede89cd1761428bb2dd04d07f7b8c6888854d915
Both payments are on their chains and locked to the same secret hash c3657805089b82dabcda983ed783f9cc825c417a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6e2b09c68a3c3592049a9cd78ee555a3ee1a0170a504aa92b6bf7769da6ecb63
- TakerPaymentSent · TakerPaymentReceived: 37a68bdbf8d23f394f0a22e1ede89cd1761428bb2dd04d07f7b8c6888854d915
- TakerPaymentSpent: 3293be347bf35402a8dc360ddf7cdcedd23c847a71b167e73f364ed01cf08f4e
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.