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.
06d6e604b9b04d38c1b319ccd8fb41a9d80a04fda08b7b5de6ab0480c20ab2dc
Both payments are on their chains and locked to the same secret hash 0b23f3e04fa284b06c8a792ec593d5bfbea75431, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 06d6e604b9b04d38c1b319ccd8fb41a9d80a04fda08b7b5de6ab0480c20ab2dc
- MakerPaymentSpent: 7a82c213d538b57f68ffa3cb145415065edb5b467fe942d62b875c603c742a05
bbbbd885b0eb695296710b4ad45acd912763d118e6950a4c2cc8bfb1dd138ca8
Both payments are on their chains and locked to the same secret hash 0b23f3e04fa284b06c8a792ec593d5bfbea75431, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1734b77d079223462b760b07c6e53e3cc27a8a2269a2e509fc4b7ff1e1829adf
- TakerPaymentSent · TakerPaymentReceived: bbbbd885b0eb695296710b4ad45acd912763d118e6950a4c2cc8bfb1dd138ca8
- TakerPaymentSpent: e8b1361c1c6f86b3e41b492e00bc115468ca13f1689b4c14912eb0903935f1ef
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.