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.
8f03201a306b313d378c86931320a38b2c613c7c1670e6d8606ece9994b3c1b3
Both payments are on their chains and locked to the same secret hash 485819e2e7ef4351b2232e609e14afc7823dbb36, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8f03201a306b313d378c86931320a38b2c613c7c1670e6d8606ece9994b3c1b3
- MakerPaymentSpent: b5db735b66a11259ed31128d42754031dd1ec82b02a24d32719d6b6f76d2250d
da81c13146947cf48af605ed29317e39a40331875c1f85b050e4da7916b26748
Both payments are on their chains and locked to the same secret hash 485819e2e7ef4351b2232e609e14afc7823dbb36, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fdd2dd36dfaccec023e165a257f0ff2ba0209fa798369dfd9c1e97a5b90ee58a
- TakerPaymentSent · TakerPaymentReceived: da81c13146947cf48af605ed29317e39a40331875c1f85b050e4da7916b26748
- TakerPaymentSpent: ca86a5f8b155e4572c78d77967ea19690fbcd6e4690f251fbf555e08741028c5
Reported by kdf-statsdb.