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.
1e134574de04efd195af8309481261976ab49dd838bcc8bcd00004c30062dca4
Both payments are on their chains and locked to the same secret hash ea3d11d861ebab2fd17a95f6ae18d68ed0c926d9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1e134574de04efd195af8309481261976ab49dd838bcc8bcd00004c30062dca4
- MakerPaymentSpent: 4d9e9e23b2869414facfbe3513b695f461dd548777cbcaa46fefd3a661c09b42
f37deb18a9d292654ac008b38f8513afe4c68de1191cca04313e7a101ec200b2
Both payments are on their chains and locked to the same secret hash ea3d11d861ebab2fd17a95f6ae18d68ed0c926d9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 31864a33a8ff62a6c7474b6fabee76840a7e08d39de05cfe7ed56f031b06a67d
- TakerPaymentSent · TakerPaymentReceived: f37deb18a9d292654ac008b38f8513afe4c68de1191cca04313e7a101ec200b2
- TakerPaymentSpent: bb079c075fa6dff2c270a48403cdb2b4b602601ff2bf34c49b179ef69b0f538a
Reported by kdf-statsdb.