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.
72fb7d5373c2191bbc0021b134a92d0a6702e122171b2b608352f8c59ddd1eb3
Both payments are on their chains and locked to the same secret hash 972caa57913db8266feb1c4b29fe63ab3c25606a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 72fb7d5373c2191bbc0021b134a92d0a6702e122171b2b608352f8c59ddd1eb3
bf42409ccec35a9b91ea8528b1d7fe0e141adcd897058160a679334089c409d9
Both payments are on their chains and locked to the same secret hash 972caa57913db8266feb1c4b29fe63ab3c25606a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 80b38e28ebde65753d2e8dcbc9b003b19772673f7dbae41efa117af8504b887e
- TakerPaymentReceived: bf42409ccec35a9b91ea8528b1d7fe0e141adcd897058160a679334089c409d9
- TakerPaymentSpent: 387e424054410f679b6bf81cd50a638874fbeae7be5527b79c965f51cc3acc54
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-8762.