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.
85bf0a143d26581b34496ad0780d6ba7b6bacf724bd484aeefbb20285f4c9714
Both payments are on their chains and locked to the same secret hash 1ed223fdf5f37f32eb7c2679ae80e8b4bafdb741, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 85bf0a143d26581b34496ad0780d6ba7b6bacf724bd484aeefbb20285f4c9714
8168e05c728de74d806a2f70dad578ea5712bed2c927dbc46aeceec5cf2b1d64
Both payments are on their chains and locked to the same secret hash 1ed223fdf5f37f32eb7c2679ae80e8b4bafdb741, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 9356b029aac8dcf201736e72e5f87a39f54865b68316ed7781d2385a8b2066a8
- TakerPaymentReceived: 8168e05c728de74d806a2f70dad578ea5712bed2c927dbc46aeceec5cf2b1d64
- TakerPaymentSpent: fc8e981f243d3b11e24e9ba1cc55be979ae5c74289a5410d51c51f30f4fabe3d
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.