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.
6e8d0569636e777c0157b5a44e50f3b0fa1d0b586e760450b6cdb060aced3a9d
confirmed on-chain via ltc.electrum1.cipig.net:20063, locked to this swap's secret hash
- MakerPaymentSent · 6e8d0569636e777c0157b5a44e50f3b0fa1d0b586e760450b6cdb060aced3a9d
c48372adc0b2493e078c606c1938cec57a4fa29fa24bbff005858654207e1912
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 · 296f4cb86485769eb5d26d7b0fee96fb1cd1db96ac577d4e40af2463504c1337
- TakerPaymentReceived · c48372adc0b2493e078c606c1938cec57a4fa29fa24bbff005858654207e1912
- TakerPaymentSpent · 1854630da2f10e0c7afa9cf82e2e2d187482b2c5d28250305aa6093db9837fed
No anomalies were recorded against this swap.
Reported by defistats-gleec.