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.
c057a5009490f5c2f7e7427f92e299a77b86e22c949a9a01a5535b5f57f67293
Both payments are on their chains and locked to the same secret hash 13df247edf60b213ce51afe6686e80f461fa904c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c057a5009490f5c2f7e7427f92e299a77b86e22c949a9a01a5535b5f57f67293
- MakerPaymentSpent: e8f853e8d1f0af731ad3fffbcdd6728ea565a175d5e43985de37260a58139ca5
fdd5782393497bf1d27be975c98997a992666482297e51f7690945d3f623e799
Both payments are on their chains and locked to the same secret hash 13df247edf60b213ce51afe6686e80f461fa904c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4afee25e706d54fffd22c0e2ccb9c5f568379a383f36dfca21433cbe773cfa2b
- TakerPaymentSent · TakerPaymentReceived: fdd5782393497bf1d27be975c98997a992666482297e51f7690945d3f623e799
- TakerPaymentSpent: b27118b2ad11348c4e0025f6308144830823e3597cea6b1e13504d03791224c1
Reported by kdf-statsdb.