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.
8d0e91b324e0a61526019b375cbc172e543bde7e90450df2cfc8b56cd8d73723
confirmed on-chain via ltc.electrum1.cipig.net:20063, locked to this swap's secret hash
- MakerPaymentSent · 8d0e91b324e0a61526019b375cbc172e543bde7e90450df2cfc8b56cd8d73723
f74fcb28bfe0e2f43b33efbb8b919bbb8bccc4d71727c1c1000b4238eb5f4585
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 · 707d161df49cc6db9cbbabc9c3a24198ce08bfe20fe02f8b123036668ce3b559
- TakerPaymentReceived · f74fcb28bfe0e2f43b33efbb8b919bbb8bccc4d71727c1c1000b4238eb5f4585
- TakerPaymentSpent · 691d9cfd193ab05f94e828af827e5117c966e228dfe40cc9ba9bf729b5c47aff
No anomalies were recorded against this swap.
Reported by defistats-gleec.