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.
0c04565fa22e5e88cabb324c5aea9abdb73a3c7fdf806bf1ad04200162d0d8f7
Both payments are on their chains and locked to the same secret hash b19cae97224428a602c145a3483ccc8d34b694c0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0c04565fa22e5e88cabb324c5aea9abdb73a3c7fdf806bf1ad04200162d0d8f7
- MakerPaymentSpent: d623863c1465ad6daa01dcfce6b4afc34f5e9cb2a5cb3ac12344915b129861b4
516e92738701983fd7d5fe9a1f9094a52b22afe00801acda5d2823ac25f4bdd5
Both payments are on their chains and locked to the same secret hash b19cae97224428a602c145a3483ccc8d34b694c0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 703d981e62e84f27c64ad978b1b385ab1414fbfa3b9259acf746bde052294470
- TakerPaymentSent · TakerPaymentReceived: 516e92738701983fd7d5fe9a1f9094a52b22afe00801acda5d2823ac25f4bdd5
- TakerPaymentSpent: 7e45fb7960b46e5a1600de7fe8f9f3e691d6b4f7ec97456e74bb309115c17620
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.