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.
094bc9a6e486be5155bd3536a4c790221771f6df5f82edd002e625a8075bbf88
Both payments are on their chains and locked to the same secret hash 5eb31daf047f8a291cfa2dc4758ac138d8eab3b7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 094bc9a6e486be5155bd3536a4c790221771f6df5f82edd002e625a8075bbf88
- MakerPaymentSpent: 936a165d371b1edd628be31df7e1ce5d636d49b1ffaa3f59b2ba908eb8fbe27f
6f26fc33bef3dfa0776a0848689bb9b1cc058868d6a60620c961e728e7e6fd91
Both payments are on their chains and locked to the same secret hash 5eb31daf047f8a291cfa2dc4758ac138d8eab3b7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c9cac1dd3492ecfded6afe455d9d591283c3a7c5e4f08acca3d4eb950da74229
- TakerPaymentSent · TakerPaymentReceived: 6f26fc33bef3dfa0776a0848689bb9b1cc058868d6a60620c961e728e7e6fd91
- TakerPaymentSpent: e9c67835fe9b2c24707eb2f5ed4d1af1ec6e13cba8d4b47820abf61f4bf3907f
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.