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.
81ea47fd71677441255bf56543f05267e9d3d10bf006bb2de0824280813e052a
Both payments are on their chains and locked to the same secret hash d1dd50f80ccf2ba7add84e66913a6e457f9e3112, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 81ea47fd71677441255bf56543f05267e9d3d10bf006bb2de0824280813e052a
- MakerPaymentSpent: eaf1b08131dbf4e88da0038bebe720d425d586f20582569c2fa7e2b2723ee260
97e80c371e89bfdeec6076b2093a7153df22b1035a6bc8003aa187d7c068499c
Both payments are on their chains and locked to the same secret hash d1dd50f80ccf2ba7add84e66913a6e457f9e3112, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2b4994d80c0cce387a7f5f545323aa3a56cf8fd2e7d4825f0316bfdb2f70c918
- TakerPaymentSent · TakerPaymentReceived: 97e80c371e89bfdeec6076b2093a7153df22b1035a6bc8003aa187d7c068499c
- TakerPaymentSpent: f45154e0a1f096d6505dca101bf64d79b36a5ef295adf671443ae2dcd17802e4
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.