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.
05907df4c12dee0655df2c32f877e8835297fcfc3094a9c8449f275b73cd0684
Both payments are on their chains and locked to the same secret hash 9a812ae90eac12741d655f0995c531bd35909976, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 05907df4c12dee0655df2c32f877e8835297fcfc3094a9c8449f275b73cd0684
- MakerPaymentSpent: 98fad561a0529ed07f8900141f73986579b1da0e44b72031da84c0dc432bf1bc
09ff3af4edf11c937551a65e6f61a5c1b58d228d05124997980d5b46d6617737
Both payments are on their chains and locked to the same secret hash 9a812ae90eac12741d655f0995c531bd35909976, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9217582388a78fa7090d796820934eec3005eb3b096810a9caeafb9602aaf770
- TakerPaymentSent · TakerPaymentReceived: 09ff3af4edf11c937551a65e6f61a5c1b58d228d05124997980d5b46d6617737
- TakerPaymentSpent: e14b7275b680eee475a55f2a959b0e39be7d1883e85ad947e5bea88de520d411
Reported by kdf-statsdb-8762.