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.
2b8d40e42a2b2f94f9124f491135dccc77716fdcde0eb4c11c057beae6b60a6a
Both payments are on their chains and locked to the same secret hash 4731cec290e0e5220d649262f7b179c64644670e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 2b8d40e42a2b2f94f9124f491135dccc77716fdcde0eb4c11c057beae6b60a6a
1784fe1523eea9d8bf758a33df2919742fab64d9c3802e6e4660c0647573718e
Both payments are on their chains and locked to the same secret hash 4731cec290e0e5220d649262f7b179c64644670e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 67d322a9d86b256b730e1fa4377206e1133a891e46300f117aa8b55721995d57
- TakerPaymentReceived · 1784fe1523eea9d8bf758a33df2919742fab64d9c3802e6e4660c0647573718e
- TakerPaymentSpent · 3f21d9fb2c1e85fe91ac6cc36f6d5920fde9c1ea3488c24a3aa9e16f61a6f67a
Reported by kdf-statsdb.