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.
c09140afe2f06b4dae66b347d83910cacb76d10d301415693982d482234feed7
Both payments are on their chains and locked to the same secret hash 2d18bcadf7129028592fe41efa19c2831bafecb4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c09140afe2f06b4dae66b347d83910cacb76d10d301415693982d482234feed7
- MakerPaymentSpent: ad0162e1d0cfea600d9a4dab7020493610e0f9237a14e320925a22247ec7c6e5
dd7a4e41aeb465eea7eeaf37b3e3a9363b83f21e0a2ecb7032ef5921155dee3c
Both payments are on their chains and locked to the same secret hash 2d18bcadf7129028592fe41efa19c2831bafecb4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: db669fd1da42328c412914d43d21c80de203f607faae7522626991aec43abe75
- TakerPaymentSent · TakerPaymentReceived: dd7a4e41aeb465eea7eeaf37b3e3a9363b83f21e0a2ecb7032ef5921155dee3c
- TakerPaymentSpent: 443096f0eda11b894663ce65e7c37862e1face808b7db45e89a2e55e1e7d26cd
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.