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.
cc9e59ae69c5475c2824f9fae9e75b71fbc88c7f7fd7db930956270162ccf784
Both payments are on their chains and locked to the same secret hash 58e5afc604e4ee4c1e9106a94c158741eba7823e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cc9e59ae69c5475c2824f9fae9e75b71fbc88c7f7fd7db930956270162ccf784
- MakerPaymentSpent: 4be56591290d9ec48926dd4d11aa33fe26343304d358590a49ec4e2b95cb007b
5e39f353f2de118fe81d40806be6de18b52ab4e678ee34bc9ac89c01873dd76e
Both payments are on their chains and locked to the same secret hash 58e5afc604e4ee4c1e9106a94c158741eba7823e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5f45e7a01dd4fe4db01a64fedda18d400d7bfa94d0815645a6530742c74b575d
- TakerPaymentSent · TakerPaymentReceived: 5e39f353f2de118fe81d40806be6de18b52ab4e678ee34bc9ac89c01873dd76e
- TakerPaymentSpent: d6eca76a7bf9dffb058eb782bf214f62e392c55c685255992a61e3bdb6c5a343
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.