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.
21875672b86f7e5eaefee7eb31741d94d60923c3eb317ba40038358548140b64
Both payments are on their chains and locked to the same secret hash d075a6aaed727907b65453d06bd89ebcb7d73ad4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 21875672b86f7e5eaefee7eb31741d94d60923c3eb317ba40038358548140b64
- MakerPaymentSpent: d7792fe03be410740b07c1f3e4622576a5d1f65aeee48319e501d4a42e37fd66
3e74ecb7647115ab1ac6e23b8c736dd484cc34e4c9213f1241e4582474754dcb
Both payments are on their chains and locked to the same secret hash d075a6aaed727907b65453d06bd89ebcb7d73ad4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 120548171defb3a905cbe25e791a974eab7abcf43329c48972d33d79fc62041f
- TakerPaymentSent · TakerPaymentReceived: 3e74ecb7647115ab1ac6e23b8c736dd484cc34e4c9213f1241e4582474754dcb
- TakerPaymentSpent: cf9e7a42b97b124d7c272a4ad23f2b7e09eaae53efb0894bc95d4376ca597687
Reported by kdf-statsdb.