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.
36bb4b0e569f0d631aa8aac99fec769c0e3e8fb7c64d1bcb705f5ce270b4e01f
Both payments are on their chains and locked to the same secret hash 69da2f9ab2796616b3a0e4d7c310e1d84d0d4ea5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 36bb4b0e569f0d631aa8aac99fec769c0e3e8fb7c64d1bcb705f5ce270b4e01f
- MakerPaymentSpent: 787c8ab729940dbdfce6ca626f6458c9bfbf19b6b653494c5378d6f1b305937c
a96da321e4a1cb6395b9f57ed00cdef2b709e3c5f2f20c6757b66090c738bb95
Both payments are on their chains and locked to the same secret hash 69da2f9ab2796616b3a0e4d7c310e1d84d0d4ea5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ea2cc23eedd32c0af425a93b5c6adc0d410d032615c7794206ec30c99916a3a7
- TakerPaymentSent · TakerPaymentReceived: a96da321e4a1cb6395b9f57ed00cdef2b709e3c5f2f20c6757b66090c738bb95
- TakerPaymentSpent: 2da600086e3fe16d39416f5bab82115f9afacbfab453a2e0b65883e965339c66
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.