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.
fbbc4b918070ba85df61e32721ecc89306c392246089429ef4f949c1f339833f
Both payments are on their chains and locked to the same secret hash a96b7832a40f2fa460c1a4e06c66c1862a9cdce4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fbbc4b918070ba85df61e32721ecc89306c392246089429ef4f949c1f339833f
- MakerPaymentSpent: 117c0bea4330f9d47ab4b04176bf81366f30f5cae523032b0b0d6fdf2793b80c
f9a73e986ce3e4542b9e716336f14510ba000bd27bdc39e090f63f369f977fe6
Both payments are on their chains and locked to the same secret hash a96b7832a40f2fa460c1a4e06c66c1862a9cdce4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fff116308b94b09ab6c2422f480e2596bf837010a7c0c69ae1882355de000f91
- TakerPaymentSent · TakerPaymentReceived: f9a73e986ce3e4542b9e716336f14510ba000bd27bdc39e090f63f369f977fe6
- TakerPaymentSpent: c85a286a8b00d0e8a250d2ac1756d04bbdc189380a4045341f0255eaa0c757e5
Reported by kdf-statsdb-8762.