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.
a7a1687228776522428c6d288f21276dd031784742796c4eab9395cd98ff46e7
Both payments are on their chains and locked to the same secret hash 8d9b61bb8b8a00de05f6d1a23483af5aabacd941, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a7a1687228776522428c6d288f21276dd031784742796c4eab9395cd98ff46e7
- MakerPaymentSpent: 8f7dbe68df53a7a579dc6449345b7a79cf790cd2f121376feb06dd025880d0dc
5f3f1e7269207f41576664b699477168e33db6212394703f7a44ef683600fcda
Both payments are on their chains and locked to the same secret hash 8d9b61bb8b8a00de05f6d1a23483af5aabacd941, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 854f02b3c4b1eacdabc82c4a5486ccd42067b3796967b2733ac4ad01f73f7290
- TakerPaymentSent · TakerPaymentReceived: 5f3f1e7269207f41576664b699477168e33db6212394703f7a44ef683600fcda
- TakerPaymentSpent: 5418f5f46ca46f8e29aa4ab65e505efa408157c301f15740849694b68902bb33
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.