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.
dcbf9868adbd949a8b5fdeb8d7e0b73c55310bc498547f2c659d06fced32f10c
Both payments are on their chains and locked to the same secret hash 63cb9168b30ba3a6382f74436a568db40bb09492, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dcbf9868adbd949a8b5fdeb8d7e0b73c55310bc498547f2c659d06fced32f10c
- MakerPaymentSpent: 97313d6805c28463f5556d908d2bcec284f3ce64f31d353bdfa13fa2fffcb1fc
4a999b2134206dde8c3d3a8bb142c9d8cfa88dc46882a269aaac50a5dedf22d9
Both payments are on their chains and locked to the same secret hash 63cb9168b30ba3a6382f74436a568db40bb09492, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 20055991adf2dbd06177614fe1e58b577ce49eaccbbb1c26e18a04215ca08d65
- TakerPaymentSent · TakerPaymentReceived: 4a999b2134206dde8c3d3a8bb142c9d8cfa88dc46882a269aaac50a5dedf22d9
- TakerPaymentSpent: bbd72a5c0a7ee89be068513930e1b4c66da6aaba8cf6af47dc04a2332e8d6355
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.