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.
7e196f44583b71e6a4797189f61d5ce5579636649d677d0182f5b71dce956fa1
Both payments are on their chains and locked to the same secret hash 7e29b05961d30bca924a1aee462db11d3ac2f4f2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7e196f44583b71e6a4797189f61d5ce5579636649d677d0182f5b71dce956fa1
- MakerPaymentSpent: dcda21647969c957eb4551fe55e9fe9aebe75de09e32f4cf15e46600473c652a
79fdfaf13ec509e020677c75e5fb76355d5b398ad98a9830949f86d50f621635
Both payments are on their chains and locked to the same secret hash 7e29b05961d30bca924a1aee462db11d3ac2f4f2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 27c6cdf88e3ab4d6e2a96bcf46c7f1bcb38977046193e5085000bb721204dfed
- TakerPaymentSent · TakerPaymentReceived: 79fdfaf13ec509e020677c75e5fb76355d5b398ad98a9830949f86d50f621635
- TakerPaymentSpent: 880141056f5b714b36adb49670b429027b2bdbd6ec29153e3de49b5eacd4078d
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.