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.
1608bd55655a0ccfabb3f44e6bc978447c314e71e9a41f7be1fd6e50c852fe0d
Both payments are on their chains and locked to the same secret hash ef6c39eee3bd2c2d11d547a7e5c49c58d13db09f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 1608bd55655a0ccfabb3f44e6bc978447c314e71e9a41f7be1fd6e50c852fe0d
890ea5595939d532cebca8524c3b2ffcefd50e60638bcfa4bb6191b06f5bcf81
Both payments are on their chains and locked to the same secret hash ef6c39eee3bd2c2d11d547a7e5c49c58d13db09f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 08ef755a130933c91cc750921d4b924aa9c2bb568ddc0f661265924097c6d85c
- TakerPaymentReceived: 890ea5595939d532cebca8524c3b2ffcefd50e60638bcfa4bb6191b06f5bcf81
- TakerPaymentSpent: 11df79e1838f3d3b430c0add6be114eadf13377c1aa2165e4e8eb52ccfb008ae
Reported by kdf-statsdb.