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.
3576ba2789097c31917b3b185877ee097ff96035b154dddef5520e33655d4448
Both payments are on their chains and locked to the same secret hash 9542f3a5e1ca6c8e80b3041e0e0c1b7fe1262dcc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 3576ba2789097c31917b3b185877ee097ff96035b154dddef5520e33655d4448
- MakerPaymentSpent: f3fb3fd8f2c64824addf1dbbf9927f3900281ac2efae669f784e973a27681e13
e2e62969cf7a4f8634ac345d45ee3d36dd7c40fe0515397bffbc5d41b670388c
Both payments are on their chains and locked to the same secret hash 9542f3a5e1ca6c8e80b3041e0e0c1b7fe1262dcc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0cbb000802ab74a315db5c44206116f6d2eaa52212091eadba24ccd7a4498724
- TakerPaymentSent · TakerPaymentReceived: e2e62969cf7a4f8634ac345d45ee3d36dd7c40fe0515397bffbc5d41b670388c
- TakerPaymentSpent: ccf75c09ae24cb1408baad16bbcd321a9d88820c7c8af9f9433dc8319c842e95
Reported by kdf-statsdb.