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.
f9c5eccb72bdee7c2902d942b0f27c0dd80f34b33b61aeef8b9afcf888a6758b
Both payments are on their chains and locked to the same secret hash 43d02fc72b80a228822877cfa5bebb6f6183d97f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f9c5eccb72bdee7c2902d942b0f27c0dd80f34b33b61aeef8b9afcf888a6758b
- MakerPaymentSpent: 3991cf85d89cc566218ee766d27241c4a3bc92fa93d58b5b85f798eb5c0b1ece
104175447ffd3e921699372face3aedbf1c5d11ec0557de3b3719eb07222258f
Both payments are on their chains and locked to the same secret hash 43d02fc72b80a228822877cfa5bebb6f6183d97f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c08cb7adf44669cf667ac99d794757ba652f55bd22ca01db5af782cae6befb71
- TakerPaymentSent · TakerPaymentReceived: 104175447ffd3e921699372face3aedbf1c5d11ec0557de3b3719eb07222258f
- TakerPaymentSpent: bcc8b6ee09f24aed67c4393a1170e9d1e2d401347f1c0c6fcaddaf91057fac4a
Reported by kdf-statsdb.