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.
22a0c83a9333464864a7cb51717da2c11b9c361410906e25437419ef92c33a65
Both payments are on their chains and locked to the same secret hash 2340e21639a541d49dd1e6abe19d7bea3ac5be5a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 22a0c83a9333464864a7cb51717da2c11b9c361410906e25437419ef92c33a65
- MakerPaymentSpent: 5cf12ea5b40e052fcdc2f28299820221530b47b7d956dfa88fd0a9fbb4c4f022
30ce3f812fbebee747ea51a1d950b3be84cb23313e97d19e61d32dc74aebab29
Both payments are on their chains and locked to the same secret hash 2340e21639a541d49dd1e6abe19d7bea3ac5be5a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aeb7ab3862b065fee56b82ac2875672976250f365ecda0c58b26b321fe5d7503
- TakerPaymentSent · TakerPaymentReceived: 30ce3f812fbebee747ea51a1d950b3be84cb23313e97d19e61d32dc74aebab29
- TakerPaymentSpent: 92cd83876ef13509707a98c84e3700ee6aace64d247ecd57599861be51b0eaa3
Reported by kdf-statsdb-8762.