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.
c6571e13582773ca4e805ce64fbf027385d2f930dee33f478e81b64220646abc
Both payments are on their chains and locked to the same secret hash 2c09794475108546bdd5a2856a12b53b5d57f52e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c6571e13582773ca4e805ce64fbf027385d2f930dee33f478e81b64220646abc
- MakerPaymentSpent: bb9299a1455354b91bdd58eb455bf8858b347496eb827e2f746ad43918173e94
b92b920edc0937f51303310a1263fe6054fdf05ff682318fc31c06c2e9ebb159
Both payments are on their chains and locked to the same secret hash 2c09794475108546bdd5a2856a12b53b5d57f52e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b91c2e2f422be2aa725bee4b49b5ef9968d3e4a9e6da84a46bc8f4e70bb500d4
- TakerPaymentSent · TakerPaymentReceived: b92b920edc0937f51303310a1263fe6054fdf05ff682318fc31c06c2e9ebb159
- TakerPaymentSpent: ea69073f98f0cf8ca8a3b35ff44d572bffc1c327d667f28349fbd59ab8141484
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.