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.
6910ed2c3af6d6ab03c39cd32ca4e9f411144081e6b23eeff0a1b7498035df5f
Both payments are on their chains and locked to the same secret hash 68b8012942c55e5cc6d5bda60bbdba8773db03e2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 6910ed2c3af6d6ab03c39cd32ca4e9f411144081e6b23eeff0a1b7498035df5f
- MakerPaymentReceived · 6910ed2c3af6d6ab03c39cd32ca4e9f411144081e6b23eeff0a1b7498035df5f
- MakerPaymentSpent · 600691cbe5688a27a34e222e94a19fd92693155a812fabf1b0d64d032c0cf63d
51f27ea85c08154087f1f5b030d173ff72880c72e2b39fe6ade4b1d47dbace11
Both payments are on their chains and locked to the same secret hash 68b8012942c55e5cc6d5bda60bbdba8773db03e2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 279467f886562d500c6c7b360f3c5a303483b25678721a08d01b0b0263c8df4c
- TakerPaymentReceived · 51f27ea85c08154087f1f5b030d173ff72880c72e2b39fe6ade4b1d47dbace11
- TakerPaymentSpent · 6f0480f924b34946f771af59410f3433fcada40e06133b217c939be4674c2eec
- TakerFeeSent · 279467f886562d500c6c7b360f3c5a303483b25678721a08d01b0b0263c8df4c
- TakerPaymentSent · 51f27ea85c08154087f1f5b030d173ff72880c72e2b39fe6ade4b1d47dbace11
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.