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.
6fe68decae4c6e45b9fa97cf8ceacf428529f7f771376fc9fdbc04697f4682d8
Both payments are on their chains and locked to the same secret hash dcda3adc591b0ccd4eedd23c5f68fb676c068708, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6fe68decae4c6e45b9fa97cf8ceacf428529f7f771376fc9fdbc04697f4682d8
- MakerPaymentSpent: 13ada375cc5f4ac6575222afba42ac7c60ebc3ef425cb335ac4379329991a3de
57daf6b1afcdcc0eb446b42ec0dc18979b4b6123428d9800adc9417602af7967
Both payments are on their chains and locked to the same secret hash dcda3adc591b0ccd4eedd23c5f68fb676c068708, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 57d58879237d44a5bd8fd706154fdd9970b77f326e896b2580b1f3ea62e9d037
- TakerPaymentSent · TakerPaymentReceived: 57daf6b1afcdcc0eb446b42ec0dc18979b4b6123428d9800adc9417602af7967
- TakerPaymentSpent: 117b081770fc1da2103f3354f4759e3dfd7c94608c194e2569bec8027944cc37
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.