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.
9a61729c31483704cf328ef31c739d98193dfb2d0645b2ad18bc424d8ea7714e
confirmed on-chain via ltc.electrum1.cipig.net:20063, locked to this swap's secret hash
- MakerPaymentSent · 9a61729c31483704cf328ef31c739d98193dfb2d0645b2ad18bc424d8ea7714e
fea32304e14a9a3a9cafda7dcd1784a8a25a4386145bfc8f8a203df1d1345bf0
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 · 648d2eebf34027f5348b2318fc961381560ff8e110ae7453319d0cacdd9f4711
- TakerPaymentReceived · fea32304e14a9a3a9cafda7dcd1784a8a25a4386145bfc8f8a203df1d1345bf0
- TakerPaymentSpent · 026f7d67a500881b1533fc88cd2736eeeec4fa3684d67794bb5a604b479836ce
No anomalies were recorded against this swap.
Reported by defistats-gleec.