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.
8ea3441de9a9641e61bb24de23a4c459fb67516f632ad56f7bcb8d059ab6c1be
Both payments are on their chains and locked to the same secret hash 35c5fa65740fbdbc44941fadde6a0a5732def994, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 8ea3441de9a9641e61bb24de23a4c459fb67516f632ad56f7bcb8d059ab6c1be
351bb919d1f0f3b2a18f9b3c902133e97eac5f6689ec7e3f026b9507d2610f75
Both payments are on their chains and locked to the same secret hash 35c5fa65740fbdbc44941fadde6a0a5732def994, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 6f80e845526064020eb04d52260508568832903c5317d6dc1e9e22c9a9d0eeef
- TakerPaymentReceived: 351bb919d1f0f3b2a18f9b3c902133e97eac5f6689ec7e3f026b9507d2610f75
- TakerPaymentSpent: e8d5c0b2e01c828e56d033589c5281405031c95f17d2c75bd34238f5d33b9621
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.