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.
eea8e62acd553b06d9a3d7d49e136107f2e6ddde4807ed7fc1ccf8867dc6f014
confirmed on-chain via polygon.drpc.org, calling the swap contract, locked to this swap's secret hash
- MakerPaymentSent · eea8e62acd553b06d9a3d7d49e136107f2e6ddde4807ed7fc1ccf8867dc6f014
- MakerPaymentReceived · eea8e62acd553b06d9a3d7d49e136107f2e6ddde4807ed7fc1ccf8867dc6f014
- MakerPaymentSpent · 251622729d24f433a73e0f4a96e3e5ef834788a2257dcd627f710313ceaafbef
00c542fefa7787cfd51395bb6e0cd65c1e615d5d1ecace9f72987c0c1b4aee8c
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 · 92d6573f9388f593db1f585ab73ad185c16502cc072cd93176d63a1d87d2b848
- TakerPaymentReceived · 00c542fefa7787cfd51395bb6e0cd65c1e615d5d1ecace9f72987c0c1b4aee8c
- TakerPaymentSpent · d28ce3aa060fa9dd03a557e1b9605e48961e86cee4cbbd202ed3e11d79b32560
- TakerFeeSent · 92d6573f9388f593db1f585ab73ad185c16502cc072cd93176d63a1d87d2b848
- TakerPaymentSent · 00c542fefa7787cfd51395bb6e0cd65c1e615d5d1ecace9f72987c0c1b4aee8c
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.