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.
218fd684492e813d99d89c31f8b5335bba98e81102a699bee5a49569b8ccf448
Both payments are on their chains and locked to the same secret hash 6e27142d2df6491633c3538dad98bb810079c91a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 218fd684492e813d99d89c31f8b5335bba98e81102a699bee5a49569b8ccf448
- MakerPaymentSpent: 758da1823022c2c44a6c86d6ebc814425479791d52b37a1215d6581ed85be084
1761a24f2dd525c5b7d4dd04a77a1e6776757f70445941b5ecc8759d8c32d459
Both payments are on their chains and locked to the same secret hash 6e27142d2df6491633c3538dad98bb810079c91a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 659a1ed3c625ca0e02316762c2c1bdf4b2024adfc59b5472f6756b565ed1ac5d
- TakerPaymentReceived · TakerPaymentSent: 1761a24f2dd525c5b7d4dd04a77a1e6776757f70445941b5ecc8759d8c32d459
- TakerPaymentSpent: c8dedfeb3f8a3e2105167b5fa263a14719258a2cdbd84e67021a2645d75e5d2d
Reported by kdf-statsdb.