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.
c3329f8ae0965cd46ef5b50bed2dea760e74e37890ed097414fe2fec7632780f
Both payments are on their chains and locked to the same secret hash f10a237034ccf8c02890ebc4a9a8d3f0322f2d32, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c3329f8ae0965cd46ef5b50bed2dea760e74e37890ed097414fe2fec7632780f
- MakerPaymentSpent: d1ed3889555f15daba1a589a56342a269f5019d4dbd97e59aa3314ac5120ad7c
ad640d2514617805ce97059f31f875c866070b5d37c56db0a87510ff4fe1bbdf
Both payments are on their chains and locked to the same secret hash f10a237034ccf8c02890ebc4a9a8d3f0322f2d32, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9e8b9b4027dc65b065fb23177c99d78e36ee67ebb73361f7a3a721bd0d207ddf
- TakerPaymentSent · TakerPaymentReceived: ad640d2514617805ce97059f31f875c866070b5d37c56db0a87510ff4fe1bbdf
- TakerPaymentSpent: 8eb020af2a89bffb3787066bbbe99a2870d7d2ca07262a33d28c9ea2c6ce9ef2
Reported by kdf-statsdb.