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.
1dac54bcd596b003b6038c3b83bf556ab412d0a739c8534bd5560af062e8fdde
Both payments are on their chains and locked to the same secret hash 539e096c50b8b3168c8fb92152e12663292dce22, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 1dac54bcd596b003b6038c3b83bf556ab412d0a739c8534bd5560af062e8fdde
8bde673cacb9f71662b3681bfb0963679448cdf98865426c5a2bc45174e993a4
Both payments are on their chains and locked to the same secret hash 539e096c50b8b3168c8fb92152e12663292dce22, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 359223989e963cadc595ddf956f143ded3e9cbea5ecdeef35b757805909d3100
- TakerPaymentReceived · 8bde673cacb9f71662b3681bfb0963679448cdf98865426c5a2bc45174e993a4
- TakerPaymentSpent · 4d98e5e02f1d2a11235d9f0b5c95f6429994286e1c248158f317a18f898d4ff9
No anomalies were recorded against this swap.
Reported by kdf-statsdb.