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.
350816126938e6cd5b86bc74852010967c959525c6cbf04bf1ea2e38a6c926f3
Both payments are on their chains and locked to the same secret hash ef4b816c2637ca20db239c7093561ec1c042639f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 350816126938e6cd5b86bc74852010967c959525c6cbf04bf1ea2e38a6c926f3
b3e281e54242964a7aeef785eb0bd26d819d3ea03f27790194f8bac1e02d2ddc
Both payments are on their chains and locked to the same secret hash ef4b816c2637ca20db239c7093561ec1c042639f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 38561524dbceddec827e6ccf7501064810c0879a78ce663ba52bcdd703ecc98e
- TakerPaymentReceived: b3e281e54242964a7aeef785eb0bd26d819d3ea03f27790194f8bac1e02d2ddc
- TakerPaymentSpent: 249f4bc42c3ee4dde1fd609dd8e399bf869312f9abac3e4bfae052b1bc4318d5
Reported by kdf-statsdb.