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.
e49598287fc2466880c8a3c57f7916b2e67675655986c6b24fae73285fa51f4a
Both payments are on their chains and locked to the same secret hash 501913393698ad679b8060a8db3968d10149bda0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e49598287fc2466880c8a3c57f7916b2e67675655986c6b24fae73285fa51f4a
- MakerPaymentSpent: 28f3089542e3083e75957acc4db72f53576a9b72c38f2885e752ca9ac76f024e
a5db246e276da499da8dca1777e69d777e8e6d9a1aa04e8dfdcf01539ecd8794
Both payments are on their chains and locked to the same secret hash 501913393698ad679b8060a8db3968d10149bda0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0427233f15a15e888a11371482151bfb6465879d62c13b05b63ee73f987f573f
- TakerPaymentSent · TakerPaymentReceived: a5db246e276da499da8dca1777e69d777e8e6d9a1aa04e8dfdcf01539ecd8794
- TakerPaymentSpent: c1170616decc4c06b9ffd412ff086375318f3b7eeb0abade493a5461793590c9
Reported by kdf-statsdb.