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.
0e9c43e247cc601b78f1980c46a76700124b7865059c39ea53da649d23d203be
Both payments are on their chains and locked to the same secret hash 077a8c4330312b5f36036b2b110a898a18870630, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0e9c43e247cc601b78f1980c46a76700124b7865059c39ea53da649d23d203be
- MakerPaymentSpent: f52f1e5af72ec4eec949e232fd98f7cf3f61b588f15a76ae30a6ff6645d9b593
87f951b1b15d16fa415048e8132e3069d0af96c27d2572bfe70ff2d68a1297b1
Both payments are on their chains and locked to the same secret hash 077a8c4330312b5f36036b2b110a898a18870630, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bcddd6074439da32139d88e56694ffc1eee4878d7e862c2251b9cd86173e387e
- TakerPaymentSent · TakerPaymentReceived: 87f951b1b15d16fa415048e8132e3069d0af96c27d2572bfe70ff2d68a1297b1
- TakerPaymentSpent: 738856da54a36dd1c27eaace8d2632e2d6a27bd62309103e859eed13d6456218
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.