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.
64c450a7e3ff8acfec2765b9e2d74ae08cd064dddd3d1123d6d4c0174e5a750a
Both payments are on their chains and locked to the same secret hash 08c4eb4a8cb1083713479cde06f21a3dd799099b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 64c450a7e3ff8acfec2765b9e2d74ae08cd064dddd3d1123d6d4c0174e5a750a
f7ded514d6166508505395a30f3b211d2f26f117e8ee2916f098f997c8ec6f74
Both payments are on their chains and locked to the same secret hash 08c4eb4a8cb1083713479cde06f21a3dd799099b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · f4a4de53e25791a7f8b38f1c5b1db3ebd231a96192386c3419965da6178ef171
- TakerPaymentReceived · f7ded514d6166508505395a30f3b211d2f26f117e8ee2916f098f997c8ec6f74
- TakerPaymentSpent · c4dfd7d536b046f5f04dc91a8b6af3b8cb529e6d7316856d0f0c9575a8e3aac9
No anomalies were recorded against this swap.
Reported by kdf-statsdb.