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.
46d34e08d25f5f760116042a255f798b44247a7ce03c5f54bfdf6dcec7206dce
Both payments are on their chains and locked to the same secret hash 2b3ce9957190af22c15f0697877166beafbeac9c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 46d34e08d25f5f760116042a255f798b44247a7ce03c5f54bfdf6dcec7206dce
- MakerPaymentSpent: f6b270726c08953a3a43baa35bef149bd2f916fb6f2eb918b17cb65035eab291
10590d18031d33807964335c1242a3949eb1fe6eaadecc9a4312ba02eb624d49
Both payments are on their chains and locked to the same secret hash 2b3ce9957190af22c15f0697877166beafbeac9c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 84680ad1e7fc1999932775c1d3fb108d4f2f76b9edb91dd0ac430e87942ac43e
- TakerPaymentSent · TakerPaymentReceived: 10590d18031d33807964335c1242a3949eb1fe6eaadecc9a4312ba02eb624d49
- TakerPaymentSpent: 1198db6a64b2b83a0b75bf1adba342d2118efc6d350c3f0f540e5b394bb4efe1
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.