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.
6345ba4967c352d0da22de40cbed81fee1347dded39fae6f4d80631496852735
Both payments are on their chains and locked to the same secret hash d299509216716023c1f48c343a3a78bee7b71093, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6345ba4967c352d0da22de40cbed81fee1347dded39fae6f4d80631496852735
- MakerPaymentSpent: e51083dd8e0cadb2def78d3a211a1a7244110fe77cc4c5627d440ab5dad223e9
d3511d0d5182656b347ec560d1bb90d9d202041a5f09ba07861fbb0aa887dd6b
Both payments are on their chains and locked to the same secret hash d299509216716023c1f48c343a3a78bee7b71093, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7ff3033ec4073570537e4da5efdbf2ac53757fb57f2b28be57d28cfe646397df
- TakerPaymentSent · TakerPaymentReceived: d3511d0d5182656b347ec560d1bb90d9d202041a5f09ba07861fbb0aa887dd6b
- TakerPaymentSpent: a636e3b5dc8d8554489b229e5d8d850bdb7f6ef8457a979fe1cbdf2f6b1d9e9f
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.