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.
b7b3b022125c622a643d7583557abc93c4d985920e6a5c64ba5c60f41ce6c1d5
Both payments are on their chains and locked to the same secret hash 531b677a200c501d2c6f231b96af7a821a0c3536, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b7b3b022125c622a643d7583557abc93c4d985920e6a5c64ba5c60f41ce6c1d5
- MakerPaymentSpent: f1114a145bc2edb5113e38c32168a4946aff4675990dc3aa79b9414ad0995a06
af7a0706dfc2cbda0cf13d41ce6c4da8df3db8a1dbdaab6b20dedb6785dc7eb2
Both payments are on their chains and locked to the same secret hash 531b677a200c501d2c6f231b96af7a821a0c3536, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7bcdd7bf6bd988863848408ad1ed5a01f568142b6dd9c555e25e1ae4914bcb06
- TakerPaymentSent · TakerPaymentReceived: af7a0706dfc2cbda0cf13d41ce6c4da8df3db8a1dbdaab6b20dedb6785dc7eb2
- TakerPaymentSpent: 8038996711a849444f4ee6add74c7cfb1892266ee4dce01ca6891cd9c00d2baa
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.