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.
045dbf57f0bf5d7f8f8f5c29691ee6a69e3e1bba896823d9fdb644da7ed802c7
Both payments are on their chains and locked to the same secret hash 4905ed3a156d8a9706e258406cc3c49c59316d79, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 045dbf57f0bf5d7f8f8f5c29691ee6a69e3e1bba896823d9fdb644da7ed802c7
3e2e8af90ab6b72ae98c907e94652e8914f424eb0750997f95402ef46accfeab
Both payments are on their chains and locked to the same secret hash 4905ed3a156d8a9706e258406cc3c49c59316d79, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 110889eb065238514911d7646033582bd21e091231c230a4b4adb168d9cce808
- TakerPaymentReceived · 3e2e8af90ab6b72ae98c907e94652e8914f424eb0750997f95402ef46accfeab
- TakerPaymentSpent · e0b8f995e2287767a4df26cd28c2d5f0299045aa186d23ff063c9c2c7b86d365
Reported by kdf-statsdb.