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.
2bbb5e78a1ee6d7671cf1a94cc1ecac3f2d692abcf38ce49bbfc0d39f0781d3a
Both payments are on their chains and locked to the same secret hash 19b89ce7b9f7ad83c48ded10e397fa95a2ef4f9b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 2bbb5e78a1ee6d7671cf1a94cc1ecac3f2d692abcf38ce49bbfc0d39f0781d3a
f47ff0a6108907b6845525f6c4a16d609dc69cf321ba32aab2d8c34aa01ebed2
Both payments are on their chains and locked to the same secret hash 19b89ce7b9f7ad83c48ded10e397fa95a2ef4f9b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 55aee2457b3fda334c440eb0f5b891400de3d74750747cf75d6458e279c38424
- TakerPaymentReceived: f47ff0a6108907b6845525f6c4a16d609dc69cf321ba32aab2d8c34aa01ebed2
- TakerPaymentSpent: 3d19842147bd0651a1788723e2c48f265076751092650dd94e929f8033e95c3b
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.