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.
49616a20bb515124ca76fdc1422cd756c392668d0ae466bb55de5e77d3b4d4da
Both payments are on their chains and locked to the same secret hash d8b82e77403ccf6de5ff354de26d589535f948e9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 49616a20bb515124ca76fdc1422cd756c392668d0ae466bb55de5e77d3b4d4da
e0fb413db9e3a7f38010c1821d0ab32393d1ce56924e2567c631f5a0132f01bc
Both payments are on their chains and locked to the same secret hash d8b82e77403ccf6de5ff354de26d589535f948e9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · c77420e34478522f129321a8ce9d45790bc1f2896f4410374e0f2e88e723637f
- TakerPaymentReceived · e0fb413db9e3a7f38010c1821d0ab32393d1ce56924e2567c631f5a0132f01bc
- TakerPaymentSpent · 1464f4b4a0eb22e9be8788e588d6d71419bc2df9df2e67790d444004493b89fd
Reported by kdf-statsdb.