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.
587ed3dcac30c6fabe6a1ff843485d9026a210257741e5322754febd180e1966
Both payments are on their chains and locked to the same secret hash 5e01e1f35caf7c7261b4984c1ad02e785fb8fa9c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 587ed3dcac30c6fabe6a1ff843485d9026a210257741e5322754febd180e1966
- MakerPaymentSpent: d54b15c76b2d7e692f97342e2dfd9bc8ff4ff379fa3edaad59d0b427994e61af
e524a6d869abc8a356857ce867242b9172ee27bb9eb8f330884ca863e4fdfd1d
Both payments are on their chains and locked to the same secret hash 5e01e1f35caf7c7261b4984c1ad02e785fb8fa9c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 004d9132f3c64d978445c2c7ca3484bbfde3abb9296d160fa7a300a11f23cbeb
- TakerPaymentSent · TakerPaymentReceived: e524a6d869abc8a356857ce867242b9172ee27bb9eb8f330884ca863e4fdfd1d
- TakerPaymentSpent: 1635ba09a832fe8cc4c36c61267de59d371bed1c03742f7f498d5294984885f3
Reported by kdf-statsdb-8762.