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.
330e37e02551d36c5fa51d28f63833318f74919a25ec0cc8add1c9b0b7bb65db
Both payments are on their chains and locked to the same secret hash 2ad7e3b21d9eba6d6bc13fe9bdd6730550a4ba40, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 330e37e02551d36c5fa51d28f63833318f74919a25ec0cc8add1c9b0b7bb65db
3e1d74d3425f03e9fa0a8081024ebfb8102991cf054bff15ada04015d60d1e08
Both payments are on their chains and locked to the same secret hash 2ad7e3b21d9eba6d6bc13fe9bdd6730550a4ba40, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 54fcfc16a411f89af5f7e2efdeeab84dbafeebdbcfadb1c6e419da63c3595fa7
- TakerPaymentReceived: 3e1d74d3425f03e9fa0a8081024ebfb8102991cf054bff15ada04015d60d1e08
- TakerPaymentSpent: 9e3a509b51f0d5e16a80608bf27bafe4301cbe33b18476e3f28b80f2c2054340
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.