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.
0f338b8f16b11c8d33aef2dd375173987e77d7dfd02f63be87072fa58dee0886
Both payments are on their chains and locked to the same secret hash 36b62a6fdc2910f05368c7060e8ab238daaeadd4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0f338b8f16b11c8d33aef2dd375173987e77d7dfd02f63be87072fa58dee0886
- MakerPaymentSpent: bf0f0c0adfc09bbedcbdad592005143036e008b7068b276e659ef86096f61853
f72dd0897154fb5c34aee6cf70930b5ebc9c0e1ea95877505db46123864f09cd
Both payments are on their chains and locked to the same secret hash 36b62a6fdc2910f05368c7060e8ab238daaeadd4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1feee9d284713c4349100ec25c268e82e6339d55d6f6adf2021786655da720b3
- TakerPaymentSent · TakerPaymentReceived: f72dd0897154fb5c34aee6cf70930b5ebc9c0e1ea95877505db46123864f09cd
- TakerPaymentSpent: d3b9ad2ead85efc82874e54b384a1e6810640730d81ffcd58cfb66551b42b62e
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.