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.
86298584dba7c0f7ce70548e2fcdb2cc1fc58efd3902771eb1ed267ca499d571
Both payments are on their chains and locked to the same secret hash b1a134bbbdfa0fb86352e27513b0661f288cb7bd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 86298584dba7c0f7ce70548e2fcdb2cc1fc58efd3902771eb1ed267ca499d571
- MakerPaymentReceived · 86298584dba7c0f7ce70548e2fcdb2cc1fc58efd3902771eb1ed267ca499d571
- MakerPaymentSpent · 07880eb7c7e2474cef2288e9b52f8b9b9fe05c4ae7bd5ecbe376c7bb7481ff9c
db010fbd126e030284aafcdc1a9f9037e250c75009328df8329ee3f9d785c1d3
Both payments are on their chains and locked to the same secret hash b1a134bbbdfa0fb86352e27513b0661f288cb7bd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b5cc4692e39f4265cb3599d803665ef7dbef269a3c397463bb7793300d3ab28c
- TakerPaymentReceived · db010fbd126e030284aafcdc1a9f9037e250c75009328df8329ee3f9d785c1d3
- TakerPaymentSpent · c6eec99b4b0cd34fd64d5b9ffe10e85fa06563dc60803eb5710b9ae9a3e7e0ff
- TakerFeeSent · b5cc4692e39f4265cb3599d803665ef7dbef269a3c397463bb7793300d3ab28c
- TakerPaymentSent · db010fbd126e030284aafcdc1a9f9037e250c75009328df8329ee3f9d785c1d3
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.