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.
19d5151e2213f7f5703c0cd3a02f82340d66a979e41e33282717f729ae6aedf1
Both payments are on their chains and locked to the same secret hash e90590d8bd367b4d146e0ea3e4f539ffb46207a8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 19d5151e2213f7f5703c0cd3a02f82340d66a979e41e33282717f729ae6aedf1
- MakerPaymentSpent: 3f7fa38939e95548aa7ff58551c3dfb87b237aebb46d259a382d0f7c648dbdaf
3f2b29453cc4d82ef4c52085bd242f4230418da538a43e76e888c9127d646f0c
Both payments are on their chains and locked to the same secret hash e90590d8bd367b4d146e0ea3e4f539ffb46207a8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 331aa8b3ffd5e8949f80303a2404fd097516d2ac3b30b281eed5952cf71285ee
- TakerPaymentSent · TakerPaymentReceived: 3f2b29453cc4d82ef4c52085bd242f4230418da538a43e76e888c9127d646f0c
- TakerPaymentSpent: f471644dff8f4a466ac438bd53e8a9581ae86356a6065c7baaf533f528fbc281
Reported by kdf-statsdb-8762.