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.
c17d8226745f483e434a7bd29f05e275cf7993d011ec64ea054a10eabef44a89
Both payments are on their chains and locked to the same secret hash e6e6bb450ea5e6890eeb9ed1486b4f7e2ab650a2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c17d8226745f483e434a7bd29f05e275cf7993d011ec64ea054a10eabef44a89
821c930ac52bbf2d9afdb6da11be3e943183b1639ecb9bdc4d62e689acc4ecf9
Both payments are on their chains and locked to the same secret hash e6e6bb450ea5e6890eeb9ed1486b4f7e2ab650a2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 966ee3a4eba580f2b141cbe41ded287cfa51a4a0a5400ca20264dbc151968896
- TakerPaymentReceived · 821c930ac52bbf2d9afdb6da11be3e943183b1639ecb9bdc4d62e689acc4ecf9
- TakerPaymentSpent · 53ce08bf132f5aad072b7065b4d51754f45629bd089ffdc52f17f4d3c31437b1
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.