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.
fda1b7481e1906cb524d0a90ed3c9f28550da3f6740ae3d132b4de7db7a71049
Both payments are on their chains and locked to the same secret hash 36db35a7946c5fee399c9a80a5b67e3db23e9c1f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · fda1b7481e1906cb524d0a90ed3c9f28550da3f6740ae3d132b4de7db7a71049
31d522fca8f8d81ca86fba90247af0f64bbf51caf513bfe6ffea584e1c798d89
Both payments are on their chains and locked to the same secret hash 36db35a7946c5fee399c9a80a5b67e3db23e9c1f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 788f1125d16cc497974e224c5e846fe3a0245f0c6a1e75046b207363b681240a
- TakerPaymentReceived · 31d522fca8f8d81ca86fba90247af0f64bbf51caf513bfe6ffea584e1c798d89
- TakerPaymentSpent · e1dc29ae3c1e21c92efe55287c3c45c460e1003dd3232af6c72e7524e0a4729d
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.