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.
466a3f0f1349b8d08adad9e8e17e3e6b36faf0f24680fbfc83f714f8895af1e1
Both payments are on their chains and locked to the same secret hash 6984d10ec55f6b0e3cf53987648aaa6602996af7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 466a3f0f1349b8d08adad9e8e17e3e6b36faf0f24680fbfc83f714f8895af1e1
- MakerPaymentSpent: ef68b7d7b967520656ce8ed6c132e1ed06a422d8c56b13c46c33c4e1039274cb
8acab69d502646ae68d7a22de41d3d26c67d7eed7ffb322e6c16e48ec8bfb8b4
Both payments are on their chains and locked to the same secret hash 6984d10ec55f6b0e3cf53987648aaa6602996af7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 140771c1e0970507539dfb448ad51dd4620fbd6105a585d6d41329ecc5348d76
- TakerPaymentSent · TakerPaymentReceived: 8acab69d502646ae68d7a22de41d3d26c67d7eed7ffb322e6c16e48ec8bfb8b4
- TakerPaymentSpent: 2f8b22af2876814500463f0b64c01d189b56aa4ea48e9bef8b95306023870535
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.