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.
f737bffb6ca8eaadc8f589ecb63cdb6495399a491bec6fd9e7b2bfa8d009e707
Both payments are on their chains and locked to the same secret hash 9f1e2ae18e34905a0fd14af698dfa70f552297c0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: f737bffb6ca8eaadc8f589ecb63cdb6495399a491bec6fd9e7b2bfa8d009e707
4d335523213c1cc7422d23884d3539765062a7466b8b6a9b6962541f76adfad4
Both payments are on their chains and locked to the same secret hash 9f1e2ae18e34905a0fd14af698dfa70f552297c0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: c51a5cbd6080dc4533a73d26b213dc3cf1e17fbe1938c93553f8290871fcbaac
- TakerPaymentReceived: 4d335523213c1cc7422d23884d3539765062a7466b8b6a9b6962541f76adfad4
- TakerPaymentSpent: 58f5ebdac73ba39c026c8858bfcee653a2c01c885b850c5d1c4f480c63bc18dc
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.