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.
c808a20008e0f0c16835c65c5eb72c652de1a74cf0d6aea79b7dcc6807e0782e
Both payments are on their chains and locked to the same secret hash dfd930b897b03b89cb99596947f9ff8d258b753a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c808a20008e0f0c16835c65c5eb72c652de1a74cf0d6aea79b7dcc6807e0782e
0dbb5c164232a159d8f802f1e49c46fb93484cc788a79d6824d305b410d807c1
Both payments are on their chains and locked to the same secret hash dfd930b897b03b89cb99596947f9ff8d258b753a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 8b99d0b0c5dcbcc6fa6525e13f7f7515550e73ef0771e277b079faad00498fa5
- TakerPaymentReceived · 0dbb5c164232a159d8f802f1e49c46fb93484cc788a79d6824d305b410d807c1
- TakerPaymentSpent · b6032153d02b2451cd66fc7a92eca1c71f0daf9f1aa89dd385df1df4d65f73d8
Reported by kdf-statsdb.