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.
35a8656ec97c9858247d336fb43b4eac7d3c9c5372a490c7614c50688d7e8d43
Both payments are on their chains and locked to the same secret hash 4c0336de757a30b9db30e1e164bc8b66eae17f4f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 35a8656ec97c9858247d336fb43b4eac7d3c9c5372a490c7614c50688d7e8d43
- MakerPaymentSpent: 35a54de4e3e966c250d2ac1a6ca16a5497cb1b6ddfe22b9afe3df9f97a6391e9
b5f0f404cb444cd968a5ac92ca7981b6cd88230a8ee255c111dd8bd0cd5f5781
Both payments are on their chains and locked to the same secret hash 4c0336de757a30b9db30e1e164bc8b66eae17f4f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a42caa478b271e228431049d964c00e4354828094c3b1a9b84d4ac310e40bc52
- TakerPaymentSent · TakerPaymentReceived: b5f0f404cb444cd968a5ac92ca7981b6cd88230a8ee255c111dd8bd0cd5f5781
- TakerPaymentSpent: 661dbabf32c0ebf131ab76af2e2928b47fe931b78ec3b1d9e44f83c4e393a243
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.