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.
1b651e6a423c7d2f1a6dc28e1d8ff2ec60853545217c29b8415f46d5474cedc3
Both payments are on their chains and locked to the same secret hash e8087e6fe7ab5aba281307beca1ee2cd55f67522, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 1b651e6a423c7d2f1a6dc28e1d8ff2ec60853545217c29b8415f46d5474cedc3
170cc6dd9586130bebcf959ce8c5a3457d05366fec4796098415833e806c710d
Both payments are on their chains and locked to the same secret hash e8087e6fe7ab5aba281307beca1ee2cd55f67522, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 75a70067607a4e91548b5b0564b6d42fdf18f5552b4bc54a1a80e37ebf950da5
- TakerPaymentReceived · 170cc6dd9586130bebcf959ce8c5a3457d05366fec4796098415833e806c710d
- TakerPaymentSpent · 35b7a0ef9872ea341c7424cd7caea7da3510b14179e9d14a025b5fa754711707
Reported by kdf-statsdb.