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.
d87b3142603ed6b68a7da7a1fbec8b7e7b8b407d4b64668ceda07a2e0bff360b
confirmed on-chain via polygon.drpc.org, calling the swap contract, locked to this swap's secret hash
- MakerPaymentSent · d87b3142603ed6b68a7da7a1fbec8b7e7b8b407d4b64668ceda07a2e0bff360b
- MakerPaymentReceived · d87b3142603ed6b68a7da7a1fbec8b7e7b8b407d4b64668ceda07a2e0bff360b
- MakerPaymentSpent · 2a6a7dda770af84449afb3185ff995377972edae5cfa5ce9f7bedf4c93372eb0
66910244639193a0dd852a256812ee68cc8976dcec5685e54db76293c8cf0ada
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 · b52b1fb57363c82fd0f75b5e2d535e12bbdf834585263783f3cd264c469e8d5d
- TakerPaymentReceived · 66910244639193a0dd852a256812ee68cc8976dcec5685e54db76293c8cf0ada
- TakerPaymentSpent · c86fdfec9f1a8441c31331a633b005788b73f6c5f855b22ee3afffaaca61d656
- TakerFeeSent · b52b1fb57363c82fd0f75b5e2d535e12bbdf834585263783f3cd264c469e8d5d
- TakerPaymentSent · 66910244639193a0dd852a256812ee68cc8976dcec5685e54db76293c8cf0ada
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.