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.
35b1cdfba41ddb2a2e328274c46dea4ce4fbfbaf3c981807e232de70db28a6c5
Both payments are on their chains and locked to the same secret hash f15676f0288eba042500bcf66ac4d63004287b93, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 35b1cdfba41ddb2a2e328274c46dea4ce4fbfbaf3c981807e232de70db28a6c5
- MakerPaymentSpent: be2b0a7087787f9c3c18653755fa85415ded7b4d65814c05b2decda796e2852b
de5912deb57b6574a62908d819c722e1032ea50eb319885f8bfcd42348194717
Both payments are on their chains and locked to the same secret hash f15676f0288eba042500bcf66ac4d63004287b93, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 540082d1d60817708e3f0eaf25731bf80a9b69cb6f965822b4b4ffcca3f0141b
- TakerPaymentSent · TakerPaymentReceived: de5912deb57b6574a62908d819c722e1032ea50eb319885f8bfcd42348194717
- TakerPaymentSpent: 313bbe3d25462c6bf30a45a654fe27946ba35d28c4ca9369abc397432b0e5558
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.