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.
828539305c81c4715211247238811125798f71001d93c4b751790fe2a5e6ee33
Both payments are on their chains and locked to the same secret hash 94ce7429b2e0cfda3c4ae62671ebfccf332a4700, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 828539305c81c4715211247238811125798f71001d93c4b751790fe2a5e6ee33
- MakerPaymentSpent: 4514dc472075b3ac5bf15b8a2345f604259e17d69974e255c8db61588ab7ed43
2666fa81e348233c6adc4c9e4fe100100794566593318d6eb2e91e035fac7590
Both payments are on their chains and locked to the same secret hash 94ce7429b2e0cfda3c4ae62671ebfccf332a4700, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9e118154c00a06d6729f87038e915601c52e6c5f2edce54395bc047d6b4bb721
- TakerPaymentSent · TakerPaymentReceived: 2666fa81e348233c6adc4c9e4fe100100794566593318d6eb2e91e035fac7590
- TakerPaymentSpent: b76aedfd51980fd094063db6c2606213f8db18017cdcc9a2c09fec6343101e9a
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.