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.
7277d969292f1f8968716118d20b9fb9302f0c8fe82c3262d5e541cba6f7b83a
Both payments are on their chains and locked to the same secret hash 3261228c8fe5aabc9edda71fa888745c3bf83fbf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 7277d969292f1f8968716118d20b9fb9302f0c8fe82c3262d5e541cba6f7b83a
ea59432c31f3827db020f0f8532b2e3692e730ddd66948aa127cadc51619d249
Both payments are on their chains and locked to the same secret hash 3261228c8fe5aabc9edda71fa888745c3bf83fbf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b9509c483613b380c9187e029b16d01be73ad58d89e53d251c3281c0c7ca61af
- TakerPaymentReceived · ea59432c31f3827db020f0f8532b2e3692e730ddd66948aa127cadc51619d249
- TakerPaymentSpent · 06d9a7d762f05c97658ec352d2c76f518bde717e34d95213d6280ad031726728
No anomalies were recorded against this swap.
Reported by kdf-statsdb.