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.
195e0a854f5d7a83d1e022c4d80d96f95f51d52027af7b5dd8ebc6ae36246b56
Both payments are on their chains and locked to the same secret hash 9f55018bceb96b06fabff93756b92cbe54b6af49, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 195e0a854f5d7a83d1e022c4d80d96f95f51d52027af7b5dd8ebc6ae36246b56
- MakerPaymentReceived · 195e0a854f5d7a83d1e022c4d80d96f95f51d52027af7b5dd8ebc6ae36246b56
- MakerPaymentSpent · 3071edb46ab7fec76ae1061da964671ef71873c56c70a047d106f627e98395f6
28f5fc572518da18144d95246b4d3986ff070ed88603a105536b181c47515290
Both payments are on their chains and locked to the same secret hash 9f55018bceb96b06fabff93756b92cbe54b6af49, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d8ad8f07ed4fb0732c8d12fae8f8927f49e2afa2c53cbf9b3ad0f1c0466044f3
- TakerPaymentReceived · 28f5fc572518da18144d95246b4d3986ff070ed88603a105536b181c47515290
- TakerPaymentSpent · bd2ea628cf8ddcd7c9643dbb21e555c95058379022084f46aeb7a7569a3d931e
- TakerFeeSent · d8ad8f07ed4fb0732c8d12fae8f8927f49e2afa2c53cbf9b3ad0f1c0466044f3
- TakerPaymentSent · 28f5fc572518da18144d95246b4d3986ff070ed88603a105536b181c47515290
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.