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.
2c963f96e4182f36c83b16cc2ca6e970f8e09644648607900e9b4420b8e81af1
Both payments are on their chains and locked to the same secret hash 4417a9205c09c222121625df3bbe9fb246199e2c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 2c963f96e4182f36c83b16cc2ca6e970f8e09644648607900e9b4420b8e81af1
9a14429ecfbf8d1217dbd9a2ab513465909bf1c1b6c027a8144780aabb649cbe
Both payments are on their chains and locked to the same secret hash 4417a9205c09c222121625df3bbe9fb246199e2c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 09b0468576ad12474af560779f9e99b9087cfb1873145d7a4e804e5823b39002
- TakerPaymentReceived: 9a14429ecfbf8d1217dbd9a2ab513465909bf1c1b6c027a8144780aabb649cbe
- TakerPaymentSpent: b9ab7c3dfc832b8a5e47b6f801cd945968ed411f4e2a7f1b5ec6642c7d7242e3
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.