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.
82e92951d1978bb05147e43b3120974f98ab94cee69aa9c9077ad123be484201
Both payments are on their chains and locked to the same secret hash 82b92313cb5a4832eb8882168e43bc53c56674de, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 82e92951d1978bb05147e43b3120974f98ab94cee69aa9c9077ad123be484201
- MakerPaymentSpent: 273a12f6e78a7466690a9f4e4d87919a31b12a76ee2a4e369fd21326abf3f523
698f87f68dced2b308ec9729703fa814a0cf7ba34fb282f6b4224d6af77beb03
Both payments are on their chains and locked to the same secret hash 82b92313cb5a4832eb8882168e43bc53c56674de, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2c4207aa90da4814928807b767262282bd1f3119e45ff509445f98ef14ddbec0
- TakerPaymentSent · TakerPaymentReceived: 698f87f68dced2b308ec9729703fa814a0cf7ba34fb282f6b4224d6af77beb03
- TakerPaymentSpent: 9ad8de1ade90e2aa02ec9f5804a1a3e4434ac1f4e74cbc2831ddf4ae564c75d3
Reported by kdf-statsdb.