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.
29adae23e29e66090010788ed870dfeb33ef4396cb8b8e87fb0d35473c796399
Both payments are on their chains and locked to the same secret hash c54cf63eb3cd5bdb3733b91982d4d659ecc393cf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 29adae23e29e66090010788ed870dfeb33ef4396cb8b8e87fb0d35473c796399
53723a1db5a13a14085445ccf74b75e39f02fabb72d480a7725dff118e2d0045
Both payments are on their chains and locked to the same secret hash c54cf63eb3cd5bdb3733b91982d4d659ecc393cf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: c6b68ec17f2280637b1c981572c9c22d5dce6657b61a8c72eae4d3ffff8b0c30
- TakerPaymentReceived: 53723a1db5a13a14085445ccf74b75e39f02fabb72d480a7725dff118e2d0045
- TakerPaymentSpent: 8594bcfb1332f74c5b0c3fb0a97e65ae3b13b33335ce68105f54fac65403ab27
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.