That would be: 7e2641f8dedd057368856912f6fc18246c4e5012ae3f93afd5af3852bfd67f05
Not sure why it comes up as conflicted, but it should be fine to just use zapwallettxes and then sending the transaction again but with a fee.
bc.i says "High S", might be an old core version or a different client entirely.
@Matijash89 which wallet software/service did you use to create the TX?
I did create the transaction with an old core version, think it was 0.8.0.0
Haven't updated the wallet for a while
After the transaction was created I performed an update to the wallet and now it's 0.11.2