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.
6512dfcd0137dd21d95eebc0948c0c18fc5bd4a17b980dc8b57492d9d3d130f6
Both payments are on their chains and locked to the same secret hash 0b5d98fc23e9129af6f4bbe0925d644a71fab80b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 6512dfcd0137dd21d95eebc0948c0c18fc5bd4a17b980dc8b57492d9d3d130f6
6f0991d575f16ca9d74db5c7e01df997c6ad79632695605ebfb5d2d4aab74473
Both payments are on their chains and locked to the same secret hash 0b5d98fc23e9129af6f4bbe0925d644a71fab80b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d6585c6d01ef26b40f8e5edb4f93c8be0fc2b7755e8fb2735e488e199e9e6c0e
- TakerPaymentReceived · 6f0991d575f16ca9d74db5c7e01df997c6ad79632695605ebfb5d2d4aab74473
- TakerPaymentSpent · 8560c646308e21fb2b8284fef592aba94fb0559f2040ef523337d043077089b4
No anomalies were recorded against this swap.
Reported by kdf-statsdb.