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.
598c15d6c38ec9857f52fc0c020b6210e431638c6a9fa7db3e4f1503c8796692
Both payments are on their chains and locked to the same secret hash e7cab574f9b1234f510ab15d95e3e12d843314ca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 598c15d6c38ec9857f52fc0c020b6210e431638c6a9fa7db3e4f1503c8796692
66b45107f805ab0633dbdc51ee4fdf91216acdda0dbdc0bb433e68436a7f801e
Both payments are on their chains and locked to the same secret hash e7cab574f9b1234f510ab15d95e3e12d843314ca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 3b6d4e35065c18feefdd3306bdf4553d2ce935b87af52a6e91ea027de332d5b7
- TakerPaymentReceived · 66b45107f805ab0633dbdc51ee4fdf91216acdda0dbdc0bb433e68436a7f801e
- TakerPaymentSpent · 1ec49787c0c28ec6d598ceaf8a8186d3276e10f1dc28004892e1d21419d952f4
No anomalies were recorded against this swap.
Reported by kdf-statsdb.