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.
e6163a646863b1be8cd7e51e010aa0f5ad358c1404045859c19932164e0c0653
Both payments are on their chains and locked to the same secret hash 51449d4e39807b6a00a64630091fe212aef0590a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e6163a646863b1be8cd7e51e010aa0f5ad358c1404045859c19932164e0c0653
- MakerPaymentSpent: c5db49761f86f1ef3c979126a2c0459d9e4031a44baae1fc32b1870752245072
19ac40395fc143b58fc1713203c86e4ab25d48d7975f48b4e374e4f488862a5b
Both payments are on their chains and locked to the same secret hash 51449d4e39807b6a00a64630091fe212aef0590a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: af9fff879d1e0c43bd54c1f84763f0860ed1c33af3151e94bb6cd214f4fc2703
- TakerPaymentReceived · TakerPaymentSent: 19ac40395fc143b58fc1713203c86e4ab25d48d7975f48b4e374e4f488862a5b
- TakerPaymentSpent: b729385f91de897df8931670b90c30c81eea44d4f5be240b667638cad3735714
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.