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.
3d423002d706d591f5dd84ca417a3535da9df834fb6944b159a90346df7aac60
Both payments are on their chains and locked to the same secret hash 4ec371505c942c50fc52ae30aa0a0b9122c06101, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3d423002d706d591f5dd84ca417a3535da9df834fb6944b159a90346df7aac60
- MakerPaymentSpent: c71d95b12a5b7e9c5822354526eb94769a02aa038de035d348e708b5da527b0f
57661f80eb3992334801a47167920421a125331675434801a01d12f1556b5766
Both payments are on their chains and locked to the same secret hash 4ec371505c942c50fc52ae30aa0a0b9122c06101, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 05caf6e4921ede49a173efbc3609bbe4b89edba6781ccc8a51cc3981f3140c73
- TakerPaymentReceived · TakerPaymentSent: 57661f80eb3992334801a47167920421a125331675434801a01d12f1556b5766
- TakerPaymentSpent: 57669eb7650cc876da0f7e8fa03472fd4d8cfd9ad6a43a4b59c7f126eda9d99a
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.