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.
4ca677d1882c85b4f55413e24d6600e3f0b8b8269b54a43c9a63d0146601876a
Both payments are on their chains and locked to the same secret hash 5007ade8412eadc91b08da5f81449ec68e5450be, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4ca677d1882c85b4f55413e24d6600e3f0b8b8269b54a43c9a63d0146601876a
- MakerPaymentSpent: 85eae7b112043fa9e673993565014e84f4fb3c5d36d2535e676a76b5f27a5649
bdae88306441cfefdaef32d7ac42da55527bc2a9ed8b7de6334bca26850e0725
Both payments are on their chains and locked to the same secret hash 5007ade8412eadc91b08da5f81449ec68e5450be, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dec08e87913c84efce505c29c1d9e9e79186f1ff55dd81062dd21e1bbea1d852
- TakerPaymentSent · TakerPaymentReceived: bdae88306441cfefdaef32d7ac42da55527bc2a9ed8b7de6334bca26850e0725
- TakerPaymentSpent: 6dad3872ebc1287a75c15328ba6a2e68e6dd8bb23f7ebf216f15e5a8aae32256
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.