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.
c5b3394fbf6e416017c63d768a83eb5d27a1daaba39e678afab506543cfc7ba8
Both payments are on their chains and locked to the same secret hash 886e5ac06dd8925c85935f25536509c0da8b3eb4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c5b3394fbf6e416017c63d768a83eb5d27a1daaba39e678afab506543cfc7ba8
f7cb2f82c72d49f1e5ef4f4bbf2127a877d1b42c700df85e743febf09c155963
Both payments are on their chains and locked to the same secret hash 886e5ac06dd8925c85935f25536509c0da8b3eb4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 8269ab0ba954c241df8721283a9aba7b1c61c347794efb64d3c87a77d484eaf3
- TakerPaymentReceived · f7cb2f82c72d49f1e5ef4f4bbf2127a877d1b42c700df85e743febf09c155963
- TakerPaymentSpent · eda3a592539a599534120cb97c399a26e4138a14ea59f1c32da8137483e8f324
No anomalies were recorded against this swap.
Reported by kdf-statsdb.