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.
f96e77c7d1da64bbf6d4b1f44076c1a65e41efc61dc75fa7f06c795e3d8537a1
Both payments are on their chains and locked to the same secret hash 147487b79e7f5c25d4d778aaf4ff42c89a14843c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f96e77c7d1da64bbf6d4b1f44076c1a65e41efc61dc75fa7f06c795e3d8537a1
- MakerPaymentSpent: 413c4c13e62a9516f21beb60f191b20f07e363cced192ac770cbbff94de3998c
d01ee7ea9cf5ebcc1496e4f1a023289e6976b6e308864252588b972eb37d34a3
Both payments are on their chains and locked to the same secret hash 147487b79e7f5c25d4d778aaf4ff42c89a14843c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4fe24af4a521b2dec76effb6a5a1b878605ee3c8e6c8a75c6915ee81c34e2bde
- TakerPaymentSent · TakerPaymentReceived: d01ee7ea9cf5ebcc1496e4f1a023289e6976b6e308864252588b972eb37d34a3
- TakerPaymentSpent: 02226e89c19d6a08b482a6e762e5e4a1b0346b67e21267b6d8751641e17644f8
Reported by kdf-statsdb.