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.
05fce0dc727607c665f593381f23e5a9b13a18269e6dfd057c67fd3d6247ce0b
confirmed on-chain via ltc.electrum1.cipig.net:20063, locked to this swap's secret hash
- MakerPaymentSent · 05fce0dc727607c665f593381f23e5a9b13a18269e6dfd057c67fd3d6247ce0b
f83b40a1de9f44b8064e3aca0d69089bb0d3a928d72fcf30e3fec98fb0212e7e
hash not checked: zet-ex-three.ewmci.online:50012: connect failed to zet-ex-three.ewmci.online:50012: connect ECONNREFUSED 193.108.119.22:50012; zet-ex-four.ewmci.online:50002: timeout calling blockchain.transaction.get; zet-ex-three.ewmci.online:50011: connect failed to zet-ex-three.ewmci.online:50011: connect ECONNREFUSED 193.108.119.22:50011; zet-ex-four.ewmci.online:50001: timeout calling blockchain.transaction.get
- TakerFeeValidated · f0623e844ef696e4fb1bc9dc8e0567b676812838c010a3a788f13cf5d4fe572e
- TakerPaymentReceived · f83b40a1de9f44b8064e3aca0d69089bb0d3a928d72fcf30e3fec98fb0212e7e
- TakerPaymentSpent · 5845f5d4337aa186ad0890b836879e0d44238be170f9a405d0127734e11cb02d
No anomalies were recorded against this swap.
Reported by defistats-gleec.