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.
702de6d1206c5e76657412b28601d40b22f2fa1dced87127fd9fc72c4f14762b
Both payments are on their chains and locked to the same secret hash 165d47db5f6cd9ca73e1038433486823228f69d7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 702de6d1206c5e76657412b28601d40b22f2fa1dced87127fd9fc72c4f14762b
- MakerPaymentSpent: eb5fb57145e3cbe5d7e00d5ac29e9563a777638e04798368b862913f28191b10
f74e5c8f2b2de0d862582238b1f1b528b4cc756c480a2f5ded02abbaaa7000fd
Both payments are on their chains and locked to the same secret hash 165d47db5f6cd9ca73e1038433486823228f69d7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6b7202b72e57487b268d90949fd835fa1b72135c11f0fa1ecd2f76766429ce7b
- TakerPaymentSent · TakerPaymentReceived: f74e5c8f2b2de0d862582238b1f1b528b4cc756c480a2f5ded02abbaaa7000fd
- TakerPaymentSpent: 7be182ef45b7ca3067973fef99cc80afa9309dd30a371f9a857adbf74e40a59e
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.