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.
3b4eb8f3923052015ff37bc879fe0e90c4baf66aa1ee3bc12d1094fb7e1fc9cb
Both payments are on their chains and locked to the same secret hash ec7f96d6696ce895299a65d3c028e8ec866cd2c8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3b4eb8f3923052015ff37bc879fe0e90c4baf66aa1ee3bc12d1094fb7e1fc9cb
- MakerPaymentSpent: 73400b3a157bd70c8c066fd1b7a63f879ae48ec0c50ab3a54ebd8a7938c2facb
0eeeeb5a9bed8c9172291a73345271aae2d3c51abc77bb0d55b8f463a6b9416c
Both payments are on their chains and locked to the same secret hash ec7f96d6696ce895299a65d3c028e8ec866cd2c8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 44a6d7e1c24e2921a5c11c3141cdcaeba5a41732dfdd3dbd4fb05685d5c9d689
- TakerPaymentSent · TakerPaymentReceived: 0eeeeb5a9bed8c9172291a73345271aae2d3c51abc77bb0d55b8f463a6b9416c
- TakerPaymentSpent: 99bfb741ba23a76c3b72a00b27471a5c4a3803e0018ab7c9b96e447c696efba5
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.