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.
3604be3099079aebd6d992dc3f25990ff352c153aa8bd2b484213906dabe260b
Both payments are on their chains and locked to the same secret hash f08f0426ef9aa6789bf14ef3a99f84a49d494d10, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3604be3099079aebd6d992dc3f25990ff352c153aa8bd2b484213906dabe260b
- MakerPaymentSpent: 7cf84d1980119208de24dd1b977f19321194b49293b7196e964a42e0cee165e8
1dd297ab8516f9222ab0126e0d6db1c6e0c36ff87bfaeef3e551d3261375646a
Both payments are on their chains and locked to the same secret hash f08f0426ef9aa6789bf14ef3a99f84a49d494d10, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7bd79eb62b23cfe0362a80b0efe3266d10f1dff1c444ac0c7055cd35c73c6597
- TakerPaymentSent · TakerPaymentReceived: 1dd297ab8516f9222ab0126e0d6db1c6e0c36ff87bfaeef3e551d3261375646a
- TakerPaymentSpent: a531d6edc77b44623450751b9c37f5d926dc0a17a5c731e2c6a5ae56927f7397
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.