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.
4d395d47de908ebf4f1e63a5f8e2d2cb159c2229b96acf40f6a321a0cbcaacb2
Both payments are on their chains and locked to the same secret hash ab1fa2ef23010a667c3cdd4cf59c8c906155226c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4d395d47de908ebf4f1e63a5f8e2d2cb159c2229b96acf40f6a321a0cbcaacb2
f3c10e4919e499ff127db5164bae8725737a6c76a75a175fc13abf9fed09b9df
Both payments are on their chains and locked to the same secret hash ab1fa2ef23010a667c3cdd4cf59c8c906155226c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 523a552a72f4698d2fda0c1daab94121a7b9f9d9a3e80ec5c17b9ffb635f3daf
- TakerPaymentReceived · f3c10e4919e499ff127db5164bae8725737a6c76a75a175fc13abf9fed09b9df
- TakerPaymentSpent · a63fe7377342cafbae9b48d1bb6a5785def2bb652dbdb04212a8e0ca86cc6157
Reported by kdf-statsdb.