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.
e19bfb3f10d8d35339bd38ea381be9e4d83ba7dadce749f46a300ca4a980dd7e
Both payments are on their chains and locked to the same secret hash 855ee08d5bb2f993c4a7881dfd23235473a210d3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e19bfb3f10d8d35339bd38ea381be9e4d83ba7dadce749f46a300ca4a980dd7e
- MakerPaymentSpent: 1350c6091e204d1b4538b487167a61b2c997c2cc34be3ba36e273ed281d9ece4
9b846ba10681e28d8f4a850407d62e04dae114c747a48a60f1f452355337e360
Both payments are on their chains and locked to the same secret hash 855ee08d5bb2f993c4a7881dfd23235473a210d3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 382e23ae06d1ab7c0160b4058a4c4d71a65bc75957b95ce3e9055e4092564641
- TakerPaymentSent · TakerPaymentReceived: 9b846ba10681e28d8f4a850407d62e04dae114c747a48a60f1f452355337e360
- TakerPaymentSpent: 66b0d280d179085ec4ff15852ec674eda85506b1517473520d78bab972ba74df
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.