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.
b83e90c8a030fa32147c4d0542359fb17dac00336260290195be06595fe2ec0e
Both payments are on their chains and locked to the same secret hash 66f8206ed60890ceff77653da369a53dfd112a62, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b83e90c8a030fa32147c4d0542359fb17dac00336260290195be06595fe2ec0e
- MakerPaymentSpent: 2ba00fd29078ff131f35a733ff3d007815691bf0f4b50aaa7be22a301b8374f9
f67b0bc3186c3f0bd9a1e549d1fe79b452eae80806e337d1cc6e1ea2ef011297
Both payments are on their chains and locked to the same secret hash 66f8206ed60890ceff77653da369a53dfd112a62, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c005aaeb035d8e02cbc23b9e5186c17ee852060b143bf0c0cc038810151389e8
- TakerPaymentSent · TakerPaymentReceived: f67b0bc3186c3f0bd9a1e549d1fe79b452eae80806e337d1cc6e1ea2ef011297
- TakerPaymentSpent: f2b06ed538b0946c5de8a8d1f5977a23f256bb1563e3d2657f86c52eb19b9487
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.