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.
84ea69d39f44460a1e7f2f1ac9eaca0dc96f944bf195034b6285bd51e6c44c59
Both payments are on their chains and locked to the same secret hash d703ae1a9fb69672dddca0d6bc86ea2af9a708bc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 84ea69d39f44460a1e7f2f1ac9eaca0dc96f944bf195034b6285bd51e6c44c59
36424ab6f824df4dfb9535f6c12e19cd46b4550bf23fabb05efe3781ec618dce
Both payments are on their chains and locked to the same secret hash d703ae1a9fb69672dddca0d6bc86ea2af9a708bc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · e3ed07fbf884bed7e0c11b8166f8fe2e2ba25c9fbb8e6b7e6a32367840c2c2c1
- TakerPaymentReceived · 36424ab6f824df4dfb9535f6c12e19cd46b4550bf23fabb05efe3781ec618dce
- TakerPaymentSpent · 9e7f9f89a9db228391eeca0c2efb50ee00722706f66c1802f890ddb932f3a784
Reported by kdf-statsdb.