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.
3905b3c9f3fb1356c6f8083a3efd0786e1fdaa07c12de7e3c927832ca78ba070
Both payments are on their chains and locked to the same secret hash 1263179224bff577e3994c4e07f3000da86ea52f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 3905b3c9f3fb1356c6f8083a3efd0786e1fdaa07c12de7e3c927832ca78ba070
7f6aced062e67cb3fbf315eed16615ae6bf4fee9e959ade4d1454851472dbb4b
Both payments are on their chains and locked to the same secret hash 1263179224bff577e3994c4e07f3000da86ea52f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: f5a521f8500803b2f8d1ae10a786566a93036bd3d465b4b8f434878c7b222817
- TakerPaymentReceived: 7f6aced062e67cb3fbf315eed16615ae6bf4fee9e959ade4d1454851472dbb4b
- TakerPaymentSpent: b2c966b7980dfcda83d94d48ac2ea969eccd06554804313d7db35b743e0886cd
Reported by kdf-statsdb.