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.
a4e9325e4640b9e06274f7f9cd6f12934287f6a1af559af49e703e4c1528098b
Both payments are on their chains and locked to the same secret hash 6c76de086022bb15db81561ce47b73ff9d2092ba, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a4e9325e4640b9e06274f7f9cd6f12934287f6a1af559af49e703e4c1528098b
- MakerPaymentSpent: dbff52667be75073dfe760dc071db0443e63d77f60671ee53b6a6da5162a2a3f
4101e22541b9bedfbb02368cdaaf248a1e741ad6e9cefbffd3f5e64ffed27832
Both payments are on their chains and locked to the same secret hash 6c76de086022bb15db81561ce47b73ff9d2092ba, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8137221cd2c31c5dae7394ec6c30e8aa008f1cac8988ba7d001a862e8bf8960e
- TakerPaymentSent · TakerPaymentReceived: 4101e22541b9bedfbb02368cdaaf248a1e741ad6e9cefbffd3f5e64ffed27832
- TakerPaymentSpent: bd9f149e1283681c2d1b6f064b5a8543a968fa6c653d699ac3417839de48c4a7
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.