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.
d0f752b06131d5956781d5411ad42eee8f6e07022172eed6fef9f013e2a0a72f
confirmed on-chain via kmd.electrum1.cipig.net:20001, locked to this swap's secret hash
- MakerPaymentSent · d0f752b06131d5956781d5411ad42eee8f6e07022172eed6fef9f013e2a0a72f
- MakerPaymentReceived · d0f752b06131d5956781d5411ad42eee8f6e07022172eed6fef9f013e2a0a72f
- MakerPaymentSpent · 6864e66956c083e57042d875feb79221a7cb5196cbe5705c450b4a2f69d974b0
f4ab83b4e3b08594478bb2704ef639342ec8f258c3daad9e97b93fd2513e6c09
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 · 29dfc7e20b3b1bfb45b8d9b682e9ac034c6f36995d7cb72d61a1e254e2c62b4a
- TakerPaymentReceived · f4ab83b4e3b08594478bb2704ef639342ec8f258c3daad9e97b93fd2513e6c09
- TakerPaymentSpent · 228f99bce096af8cd7a660e2a62b0c0dce3c8313c3361b6bd93886a40fd37b0d
- TakerFeeSent · 29dfc7e20b3b1bfb45b8d9b682e9ac034c6f36995d7cb72d61a1e254e2c62b4a
- TakerPaymentSent · f4ab83b4e3b08594478bb2704ef639342ec8f258c3daad9e97b93fd2513e6c09
No anomalies were recorded against this swap.
Reported by defistats-gleec.