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.
c1e9f1691ceaf30ab9b78dae2a90e1cf5d249321cb345aa8ac6b5952cf8bc096
Both payments are on their chains and locked to the same secret hash e3f23d245abc9e05cd3f8196dee9b2354e565aec, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c1e9f1691ceaf30ab9b78dae2a90e1cf5d249321cb345aa8ac6b5952cf8bc096
- MakerPaymentSpent: 973be79175c1cb452a94564dc68e2b41cbbc3c23bbcc36a2e7386f9f526a891e
200713cf563cfd146fbd0d168b5bfb75bc602b2f7024c3f4a4dd1bf9783a6f18
Both payments are on their chains and locked to the same secret hash e3f23d245abc9e05cd3f8196dee9b2354e565aec, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ba4399fbad066083a34c07f9d0049cc0eaf3954bdcd10262fc32ab0cb92d26e6
- TakerPaymentSent · TakerPaymentReceived: 200713cf563cfd146fbd0d168b5bfb75bc602b2f7024c3f4a4dd1bf9783a6f18
- TakerPaymentSpent: 2d61de1be27ff66aec588134190e47f9d6387a7e88c73ca75ecc6ce71399babd
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.