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.
24bc054472ad073ab6a7541701829846579c6ec08e31654e2bceee148f558135
Both payments are on their chains and locked to the same secret hash 5356204ce5a81e539dbd27ad833f732bc85dd64b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 24bc054472ad073ab6a7541701829846579c6ec08e31654e2bceee148f558135
- MakerPaymentSpent: aed71f625f5eb53ec60bb9a7ea610e8ce8a893cefc86095120db80f08ac8d3c3
c7dd8f9f36548dc183dfb81984298cb5c52fa4b26f00597023fb44e98602fbf1
Both payments are on their chains and locked to the same secret hash 5356204ce5a81e539dbd27ad833f732bc85dd64b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fe29237d739ea9009472b02d43b9301815dcb01105153cdf8b17d7b9f2e9b08d
- TakerPaymentSent · TakerPaymentReceived: c7dd8f9f36548dc183dfb81984298cb5c52fa4b26f00597023fb44e98602fbf1
- TakerPaymentSpent: 634ad5a8e417450ae41710ad955a795ffae441ab9e66935a1e3842743b5e2302
Reported by kdf-statsdb.