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.
95f38e9c253109bb05cbc2a1968153498a3e2d14ee0bef520fdcf17357afcd43
Both payments are on their chains and locked to the same secret hash bb82fbe36919a899b6bb1943839dda7a70f45c56, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 95f38e9c253109bb05cbc2a1968153498a3e2d14ee0bef520fdcf17357afcd43
- MakerPaymentSpent: 02de9b7ece9b25101c4303333a21706ec9ea8b33ce141421f2891adef48994a1
d6ce7da80662da6867a5abaf36f36b0fdad2fbc32727bb1e156efe631472121f
Both payments are on their chains and locked to the same secret hash bb82fbe36919a899b6bb1943839dda7a70f45c56, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c04e9e0c5758c05da92427a292b858e94b92c384504d88e89ca8aa377296d5aa
- TakerPaymentSent · TakerPaymentReceived: d6ce7da80662da6867a5abaf36f36b0fdad2fbc32727bb1e156efe631472121f
- TakerPaymentSpent: 1e57918be31b8701db3582097895bf74484eefe6c3e41b58b393ad9d9b9046af
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.