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.
7bb2262c220534287b1f0ef16823e81cf9271fc8743a56e423874edc2258c7d6
Both payments are on their chains and locked to the same secret hash ca048f300e6dcb75dbe3621ba123ca966922c5a9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7bb2262c220534287b1f0ef16823e81cf9271fc8743a56e423874edc2258c7d6
- MakerPaymentSpent: 4f988e0e478fa261ec80842b7f2bd7fdcd459f8a2f70e9355a0895818215f87f
d40658a17357e85bf97330079df4aaf64d3d8e0cf22cad41b2508a8ec6e74262
Both payments are on their chains and locked to the same secret hash ca048f300e6dcb75dbe3621ba123ca966922c5a9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b43407c4d2971e8f96d41e42870e9664b7d40d79cd32ace262e1ad1590ebf6d0
- TakerPaymentSent · TakerPaymentReceived: d40658a17357e85bf97330079df4aaf64d3d8e0cf22cad41b2508a8ec6e74262
- TakerPaymentSpent: 198443b5db815538f3f8d983fc9060721af3448dfeef6e51b88e5ac16fbd1acc
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.