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.
49829961e33b417b729e576ba02d19eabe1fb86dd80da27fd2eef9206282ee2c
Both payments are on their chains and locked to the same secret hash c73585c4989c41ca6270a3ccd73c3fa0152692ea, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 49829961e33b417b729e576ba02d19eabe1fb86dd80da27fd2eef9206282ee2c
9e86f1a1a8378ee94c6c09eda715383f3c7c92f338a493827bc3e5da2977db21
Both payments are on their chains and locked to the same secret hash c73585c4989c41ca6270a3ccd73c3fa0152692ea, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 831625f76cd383964ce2a0167bfff2934df324bf43f3991a9957eb9aa0125fc9
- TakerPaymentReceived · 9e86f1a1a8378ee94c6c09eda715383f3c7c92f338a493827bc3e5da2977db21
- TakerPaymentSpent · a600128d39b5cbaf221ab5b0e733cc6565d154387dec675fa5422ad28e25f154
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.