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.
4a88baab5d31600919ab6bd00b9f701ca22f81690863bd3bbe486bf104c87568
Both payments are on their chains and locked to the same secret hash f4d7cf77956b609fcbeaf3b8b4b5a02bd5685008, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4a88baab5d31600919ab6bd00b9f701ca22f81690863bd3bbe486bf104c87568
- MakerPaymentSpent: 22490f404f7f8cebb46e7199ab14ca2eb078c343df390d20c6677532cc5483f3
e0dc1fdc9a1aa16e84bb6f7649f7317bb03d558300fa776248a3e87096d35913
Both payments are on their chains and locked to the same secret hash f4d7cf77956b609fcbeaf3b8b4b5a02bd5685008, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5d50b6a00f97fbc52c35d149b3e506d15fb0e265a4b6e0aa50a9c9961b05e462
- TakerPaymentSent · TakerPaymentReceived: e0dc1fdc9a1aa16e84bb6f7649f7317bb03d558300fa776248a3e87096d35913
- TakerPaymentSpent: b2b02df6af40a821580955134e04212eb59b2d35a4f4f224f92262ae86878c2d
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.