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.
6cfdbe669856bdf6a348fd4a11c9b0c947dc0e1014eca2b84cab87478858e08b
Both payments are on their chains and locked to the same secret hash 8e3e8e8b36e380872084a0c3ca56d9afeab38f42, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6cfdbe669856bdf6a348fd4a11c9b0c947dc0e1014eca2b84cab87478858e08b
- MakerPaymentSpent: 25dac54a131bb2fb12deff8f328c1e1947684138ec67cfe9396db6a5348ede6f
f87f9858bf7773e0ee9979faecfd91be745bf71efccd05148206e9aa219080d2
Both payments are on their chains and locked to the same secret hash 8e3e8e8b36e380872084a0c3ca56d9afeab38f42, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bf23adf94f7a780d2c52e1a2f3ccd205d6acf60f36e22c8feb4effab6ab33432
- TakerPaymentReceived · TakerPaymentSent: f87f9858bf7773e0ee9979faecfd91be745bf71efccd05148206e9aa219080d2
- TakerPaymentSpent: 479edd4ceee97428e7cbf58372218a95a1837fe2018773085023362684c9546f
Reported by kdf-statsdb.