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.
202c3af5a9c7b53817208d012e19eba8706430cb4742e9f7e939586bed4e62a9
Both payments are on their chains and locked to the same secret hash 2cdf90f2f30dc2bab963b1b401ceb1891f5cb4b0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 202c3af5a9c7b53817208d012e19eba8706430cb4742e9f7e939586bed4e62a9
ec243e6aba2c886da942599af3be5ed3ab549b64c5e685a77c04fb38945bf928
Both payments are on their chains and locked to the same secret hash 2cdf90f2f30dc2bab963b1b401ceb1891f5cb4b0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 660b6a586b16e7a974ba3622f83fb3e609fd0c7051b2edae5eeb8a042bcca6ed
- TakerPaymentReceived · ec243e6aba2c886da942599af3be5ed3ab549b64c5e685a77c04fb38945bf928
- TakerPaymentSpent · a330d6a25605a5420046781f84d1d86ae1edc67fb385d23d17ebda6feb15da28
Reported by kdf-statsdb.