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.
7223f67a3a4c210461ebab3ee6b2d6ce6a04540eb35243da0bfec4e3bddd137f
Both payments are on their chains and locked to the same secret hash 0b2c2db4c3905af849405b6579efff121df3e956, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7223f67a3a4c210461ebab3ee6b2d6ce6a04540eb35243da0bfec4e3bddd137f
- MakerPaymentSpent: 994b92921905b4451ea19cf5f42b20d31258627b8c802b5e13d5520fac8d7744
4a300a1785fb3346222e5ec7ce0649ec72fc65dfa1c34f62857f4874739e7e44
Both payments are on their chains and locked to the same secret hash 0b2c2db4c3905af849405b6579efff121df3e956, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 1136f2aa75b2951a5c888dec787edcc254ce590e1d906dfcbb68269c0fa6546c
- TakerPaymentReceived · TakerPaymentSent: 4a300a1785fb3346222e5ec7ce0649ec72fc65dfa1c34f62857f4874739e7e44
- TakerPaymentSpent: 9b737432d855df40efbef6456e237ba80eda1c5d62f18126e97eef01bbad52d2
Reported by kdf-statsdb.