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.
ab52a709aaf8dea592dcf56f73f8ed8419e3d4a691f24fc4dc13c198891eaa47
Both payments are on their chains and locked to the same secret hash c93db1aa0f9d596d1a8045245877de9bdf0e1e4a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ab52a709aaf8dea592dcf56f73f8ed8419e3d4a691f24fc4dc13c198891eaa47
- MakerPaymentSpent: 12cef8cdd1c54885261656913f9ea8b0a9718d07e044093e254db5f52d5e2893
c749f67c549c722d281b84c664081eeb1d0c4e1a171ed896d013cbb443d993f0
Both payments are on their chains and locked to the same secret hash c93db1aa0f9d596d1a8045245877de9bdf0e1e4a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 224b1ca7f19c5eb4b1d07957237920cdb7259b636a38339b892f250976e3eb21
- TakerPaymentSent · TakerPaymentReceived: c749f67c549c722d281b84c664081eeb1d0c4e1a171ed896d013cbb443d993f0
- TakerPaymentSpent: dcf9d3428b0a4d1c78abcfab726e34de24c6e6e1c20a7e17c8fc9c4ac2b8dbb6
Reported by kdf-statsdb.