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.
b810f618d1204fb37564dd9e2f72bd7d48e758aee18065e686b6eafa13ba9adf
Both payments are on their chains and locked to the same secret hash 79e5e9193bfd078767d2715d0d2033d07eca0849, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b810f618d1204fb37564dd9e2f72bd7d48e758aee18065e686b6eafa13ba9adf
- MakerPaymentSpent: 66bb35ed4b056fd05903e961138be5fe68192d6d987dbb9049313796de9a3b42
5fe310683af529b0d2542c688f47ce3fc33f6a206ad8744d0eced65c94f8a266
Both payments are on their chains and locked to the same secret hash 79e5e9193bfd078767d2715d0d2033d07eca0849, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b0820812d9a2a9ddf232bb1d533daf833894dc9225ded8002a1662fb84638d69
- TakerPaymentSent · TakerPaymentReceived: 5fe310683af529b0d2542c688f47ce3fc33f6a206ad8744d0eced65c94f8a266
- TakerPaymentSpent: e610ac4f7298d19c633643e12dc6faa2e789631f096e469614a0b645c6776b0b
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.