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.
360ff7782a6d31e98701510a5207d04c355ff6b47f49253f0fff85527310b279
Both payments are on their chains and locked to the same secret hash 0e3d8d3d747453838c02e5e014bf64a9dc81f54d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 360ff7782a6d31e98701510a5207d04c355ff6b47f49253f0fff85527310b279
- MakerPaymentSpent: 311222204f64556fc33eb867ec4bf5a9ac7f4a96944f238b2644f830f21b1c67
89aef8047c0ea34d6313d8c8ee2703407947dd48d4c193f75bdc703d0c70d1dc
Both payments are on their chains and locked to the same secret hash 0e3d8d3d747453838c02e5e014bf64a9dc81f54d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f02f7c9c5d506f584ff5f24530ed13943df5d0a853c8daec48d4f2dc60c1d92a
- TakerPaymentSent · TakerPaymentReceived: 89aef8047c0ea34d6313d8c8ee2703407947dd48d4c193f75bdc703d0c70d1dc
- TakerPaymentSpent: 778d9acabfe8176ede972d840196b92f16f201f7a59d7358caf40d83b059e850
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.