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.
4c077a596b044b762a59b28ad8a5d34f0bf5f320137b724af9ea910ab35ca9f1
Both payments are on their chains and locked to the same secret hash 73eb50eab9c12e6e8f1d66dbc091c8abadd5bcb5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 4c077a596b044b762a59b28ad8a5d34f0bf5f320137b724af9ea910ab35ca9f1
201f4e277486fbe581a3b6bba2879d7e623d4cbe7a692863fa30f8886b6d9d81
Both payments are on their chains and locked to the same secret hash 73eb50eab9c12e6e8f1d66dbc091c8abadd5bcb5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 30a0d96a38eea112738bfc8427aab558a0e2b0c280a89bd1fbd250aa427b7c22
- TakerPaymentReceived: 201f4e277486fbe581a3b6bba2879d7e623d4cbe7a692863fa30f8886b6d9d81
- TakerPaymentSpent: 681b625e3bec161d68fe613f3067c3bdddb58b31a612edec846c6fcc486a33ab
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.