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.
8cd222b03fca485c1661eee7da37fb1ea76c583afde53f81ce133cc502e57df3
Both payments are on their chains and locked to the same secret hash c19ed192c538f95021affa87376dfbb5eb1d841d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8cd222b03fca485c1661eee7da37fb1ea76c583afde53f81ce133cc502e57df3
- MakerPaymentSpent: c1e49537011643479009438dfc83006d82ee569fdf47a5e0faa855740c9dae11
8366d6db3d8b57805f215bca711ad949d7f9a3c297906bb6fb7435b157eca89f
Both payments are on their chains and locked to the same secret hash c19ed192c538f95021affa87376dfbb5eb1d841d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ae0615c04add669f6269163eebcd3cdc0fa9e7c04f3c19c6cbbe10a9de191f13
- TakerPaymentSent · TakerPaymentReceived: 8366d6db3d8b57805f215bca711ad949d7f9a3c297906bb6fb7435b157eca89f
- TakerPaymentSpent: 79d1078024205e98db7ae48313ec923dea98e27cbf77bde5abb65ecc2e8cf9e4
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.