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.
20f6b2baef0453f6919ce6755893f2449f11133df51270d1a16c31bfae77480b
Both payments are on their chains and locked to the same secret hash d1860f5cde4328ede18edf134afc4132122f1643, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 20f6b2baef0453f6919ce6755893f2449f11133df51270d1a16c31bfae77480b
- MakerPaymentSpent: 0d249103028fb9c8ee7708698e15164d0689b0a4c23954ea329336866facfb0a
3f823d29eb495e4c222b9d8348a14eea67773526eb901f560f48a09fac74e113
Both payments are on their chains and locked to the same secret hash d1860f5cde4328ede18edf134afc4132122f1643, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 511326577aa9b2f5c1392035092ff32ac9f411d48125809deaf1c734251cec80
- TakerPaymentSent · TakerPaymentReceived: 3f823d29eb495e4c222b9d8348a14eea67773526eb901f560f48a09fac74e113
- TakerPaymentSpent: a3fa49006b010c1fbba152e92d89e113feee09eacd20568ca4d13c926e1a9d7d
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.