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.
ed9ac85b506fe0c8267a6666c51471ce7615ad2b7a2afc39bcdb1e49d93ab918
Both payments are on their chains and locked to the same secret hash 0f8361cc95115defbff79be0b9536c9ea45d6e5b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ed9ac85b506fe0c8267a6666c51471ce7615ad2b7a2afc39bcdb1e49d93ab918
- MakerPaymentSpent: 30b47e6f0649ce74ac9d44c48514eca33f86ecc61ac0e46dccbd9c72b4aeb147
ddc2f5880e3ffa0ac275754bcd459189785c995931c900c0567b6afbec9aa4b0
Both payments are on their chains and locked to the same secret hash 0f8361cc95115defbff79be0b9536c9ea45d6e5b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0bdb275c243728f761a13c68e98f1372132407651990ce2640614daa7300ad44
- TakerPaymentSent · TakerPaymentReceived: ddc2f5880e3ffa0ac275754bcd459189785c995931c900c0567b6afbec9aa4b0
- TakerPaymentSpent: d6fb5c1c9bf6612eb56fa4818ab5972048b6d5b15fab071476606724c4856a81
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.