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.
2dd992b2e9a4d82b43a6f2c6417cab4365c6c448eaa8783548735a62a54fb7ad
Both payments are on their chains and locked to the same secret hash 38f3958834bfeb5ff3e3ec8e89e3df012cc80fef, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 2dd992b2e9a4d82b43a6f2c6417cab4365c6c448eaa8783548735a62a54fb7ad
61a963dc537f7152158077315d6fb42a840938c9278d3e54f5dff7785d05e917
Both payments are on their chains and locked to the same secret hash 38f3958834bfeb5ff3e3ec8e89e3df012cc80fef, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 24e1f4f62269492e80eb6775ab98f71451887b757ef124b76d89f8ba544711c2
- TakerPaymentReceived: 61a963dc537f7152158077315d6fb42a840938c9278d3e54f5dff7785d05e917
- TakerPaymentSpent: 3d609fa28b3a6783ecc86bc259ed00a7185cbe01eac8aa62d67f54f0006e4d29
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.