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.
44e0b1fa8436669f5149f9150adc653fb744b7649d7e320aff183a64758d9114
Both payments are on their chains and locked to the same secret hash 6b401da85564e32c33099a2682f58788b96276fc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 44e0b1fa8436669f5149f9150adc653fb744b7649d7e320aff183a64758d9114
- MakerPaymentSpent: 7aeb5f46865e1bcf378cbf23de19db169cfdd96a61a1c4812e0cabbe351aa579
f0d7cba078f1002b68fc610c8ae6efe8bd1c6882f2e9c350db22efbe517cad40
Both payments are on their chains and locked to the same secret hash 6b401da85564e32c33099a2682f58788b96276fc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aada36a6241d5c90d304ba14dc5f3f692c204545c60f7762cc6035997507a8df
- TakerPaymentSent · TakerPaymentReceived: f0d7cba078f1002b68fc610c8ae6efe8bd1c6882f2e9c350db22efbe517cad40
- TakerPaymentSpent: e018646d2a5ac3c6c78d37904a625e03337eadd49d8f7a9050b9920dc73b16e9
Reported by kdf-statsdb.