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.
0270b4dac9fbfacd84c1d2ca839a796077b491ee3d9ac0d07cbb0ab5934e514c
Both payments are on their chains and locked to the same secret hash 6d039083d06b0a09153af15247ab6b2b19cd7ce0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 0270b4dac9fbfacd84c1d2ca839a796077b491ee3d9ac0d07cbb0ab5934e514c
cc87b2175c55c99331b4f2991a1492bb349ebf1036da66a493bb9bb95963948d
Both payments are on their chains and locked to the same secret hash 6d039083d06b0a09153af15247ab6b2b19cd7ce0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 1fb4396d184e0d6e86237bc476c97212041419c0a17ec2618b93e74b2784d193
- TakerPaymentReceived: cc87b2175c55c99331b4f2991a1492bb349ebf1036da66a493bb9bb95963948d
- TakerPaymentSpent: c8ea8ed93918172a9de97a15fb9e5c999a5341355aed1c3952b3573f5d04f699
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.