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.
745750adb3d9f2ccc0f6c21c3eec30a59cb4da769b03466b3b2905c029220346
Both payments are on their chains and locked to the same secret hash bb96de0efd6c5f573f369fd6a82d0926190930a5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 745750adb3d9f2ccc0f6c21c3eec30a59cb4da769b03466b3b2905c029220346
- MakerPaymentSpent: c5bb5d1108433c4a3989a0158beeeb7bff18bdd4fd562fad133059f047c2eed5
50a35703891b1743b0eb1c411916c3b281c6ebe9fa613072cfab5ca40867548d
Both payments are on their chains and locked to the same secret hash bb96de0efd6c5f573f369fd6a82d0926190930a5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: be3b85a43a71ab04682d5b4004cc9d1ed1d3eabf484ac3967a5b947c143b2b02
- TakerPaymentSent · TakerPaymentReceived: 50a35703891b1743b0eb1c411916c3b281c6ebe9fa613072cfab5ca40867548d
- TakerPaymentSpent: a40a7d57b5fec76b2d5dd5063d9166916bdbb3e30159eca400c61afda10e1cdf
Reported by kdf-statsdb-8762.