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.
b41a482b489abf3bab32befb62a28533541e6f7a1cdf8d9893df6d9e73244696
Both payments are on their chains and locked to the same secret hash 3daa3ddcd13185eadb5426d4f4eba1f4cc588b76, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b41a482b489abf3bab32befb62a28533541e6f7a1cdf8d9893df6d9e73244696
- MakerPaymentSpent: 34fc0c3d06b46a8a60182dbda277f8681671ead1157f454e25291afead86a4e2
424408798bea1cd79e8dea074dc24f6404ec3680c7ec8cbc6f86cf4f5fb8decd
Both payments are on their chains and locked to the same secret hash 3daa3ddcd13185eadb5426d4f4eba1f4cc588b76, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5297f317b3a66271afbf36748be4580d92c9f1dcb45ae28e24c7a59d37745559
- TakerPaymentSent · TakerPaymentReceived: 424408798bea1cd79e8dea074dc24f6404ec3680c7ec8cbc6f86cf4f5fb8decd
- TakerPaymentSpent: 0e01fc3d3ea083f4353c10975392ce1c478f743cc9110ce83716e74128a9cfea
Reported by kdf-statsdb.