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.
d5944800b3682400df3e4d016836fe1e43b9ead4265ac6130ae4a3311e4f2825
Both payments are on their chains and locked to the same secret hash 333c0703bc9ed862157cfdbb41176a166d6f5283, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: d5944800b3682400df3e4d016836fe1e43b9ead4265ac6130ae4a3311e4f2825
b12ad9c7126a42f7503e2600ead23fadb639af5667a62a8ad4473e6cc8fbf08b
Both payments are on their chains and locked to the same secret hash 333c0703bc9ed862157cfdbb41176a166d6f5283, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: b3dfbf70da1e0b673549c3e440d7018148c2817adce8994e576e0c7c75fbdfff
- TakerPaymentReceived: b12ad9c7126a42f7503e2600ead23fadb639af5667a62a8ad4473e6cc8fbf08b
- TakerPaymentSpent: 28fb4d6fd9a6475572d2633aaeb938a1e7011f846e43a7cc051de8d4768a2028
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.