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.
720b86136c7d5f3fcdf4841df515488ad50b40113681af2e63d593e336e334af
Both payments are on their chains and locked to the same secret hash b52542f09383e4e82063f3e6564260d57a698ddb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 720b86136c7d5f3fcdf4841df515488ad50b40113681af2e63d593e336e334af
- MakerPaymentSpent: bc4a100c05d921bd94e2cccb377cb7baddfa9bd1d688e85ce63f9ebcf6bf971a
fcf832f20c264e37a5b06bbc9ce56c95f05ddcea6206519087bbc47a49010db3
Both payments are on their chains and locked to the same secret hash b52542f09383e4e82063f3e6564260d57a698ddb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7ed41f176f080ab5798ce95ade566cc25872333407a72129ca856369c2b0ca4d
- TakerPaymentSent · TakerPaymentReceived: fcf832f20c264e37a5b06bbc9ce56c95f05ddcea6206519087bbc47a49010db3
- TakerPaymentSpent: 80f34ac8d96867a13d09d3889b3ea10d2a80cac89149b500617379685f7ff552
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.