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.
fe19f34e0b4257146c2900b47e9c9bb224df9960dd14a16b18ecdd12d8cd7750
Both payments are on their chains and locked to the same secret hash b4a9eca6025776805a4fc4795ef5423ab2d31202, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fe19f34e0b4257146c2900b47e9c9bb224df9960dd14a16b18ecdd12d8cd7750
- MakerPaymentSpent: 3352601d3db280c8175e3b82ef4c8c2f95c77053dae29d92482862583f6d410c
c443ca3ca459e25989e7de3352e2f29c328cfdb72221c5a1e38e35f6c3cf29ab
Both payments are on their chains and locked to the same secret hash b4a9eca6025776805a4fc4795ef5423ab2d31202, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 29a420df8bee45401e48ac6140c70af1330dfc50d702e9bc5a904323cf7d0d12
- TakerPaymentSent · TakerPaymentReceived: c443ca3ca459e25989e7de3352e2f29c328cfdb72221c5a1e38e35f6c3cf29ab
- TakerPaymentSpent: f50243c91f1d24b205eee608569ad61f4ca52eec0b00a4781275bb7f64f19ef6
Reported by kdf-statsdb.