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.
9087835068e6470a2ddc0d2cdb2b3528e1fea7688065168c3e17028845678256
Both payments are on their chains and locked to the same secret hash 06a9bceaa043fceed1091e2cf6a1c740224473ec, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9087835068e6470a2ddc0d2cdb2b3528e1fea7688065168c3e17028845678256
- MakerPaymentSpent: cf052dc70a3563b1f167a5fb5a9845ab9535ef86146be14ecb498a0b7365a247
5ec7f905e7d771d270773fa3aabac17e824f1f3838d03c495d55891d5a0eb335
Both payments are on their chains and locked to the same secret hash 06a9bceaa043fceed1091e2cf6a1c740224473ec, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 05db41b62f41deb06b48c3285a65ecb41007bb7104a95b118fe863e2fc936a0b
- TakerPaymentSent · TakerPaymentReceived: 5ec7f905e7d771d270773fa3aabac17e824f1f3838d03c495d55891d5a0eb335
- TakerPaymentSpent: 2f128c8b0c9900267caadf138d15a5000cb9c00eca7eec317ad0328e36be9164
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.