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.
98e1148a6b0da70517fc04e49929e9d6c97f0ef9b5ceedb365e37a55b07c0fb1
Both payments are on their chains and locked to the same secret hash 6ae371db4ee0774cc9863f03afb51c7b10646499, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 98e1148a6b0da70517fc04e49929e9d6c97f0ef9b5ceedb365e37a55b07c0fb1
- MakerPaymentSpent: ce9b570a8659c17a7b9ff92a5b7d439bc3326696bdba50de606d969fa5ac2326
bfdb36f7f1b4c9781be3b22258505bbe9c89307c52235991f1993ec12866ee44
Both payments are on their chains and locked to the same secret hash 6ae371db4ee0774cc9863f03afb51c7b10646499, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: de79e89295f72a105564e9637a50db529349bd872d32202bca13d0092fbb03e4
- TakerPaymentSent · TakerPaymentReceived: bfdb36f7f1b4c9781be3b22258505bbe9c89307c52235991f1993ec12866ee44
- TakerPaymentSpent: a2dfee0d1a039c29ddca5135da257ea2b62b87980e6661ea479ce0bb60231b4d
Reported by kdf-statsdb.