the problem here is that this is a 373 byte transaction with a 2592 sat fee. That's only <7 sat/byte.
In order to "fix" your problem, you need to re-broadcast your raw transaction:


you can use google to find places to broadcast your transaction.

After the transaction has been broadcasted, i'd suggest you to create a CPFP transaction... That seems to be your safest bet, but first, you need to broadcast the transaction, so it's in the mempool of most nodes.

Unrelated:
Public service announcement:
In the past i was able to help people using 3 tactics:
1) push their transaction to antpool's priority queue
2) push their transaction to ViaBTC's free priority queue
3) give them advice on how to create a CPFP, RBF or double spending the inputs of the unconfirmed transaction

However....
1) Lately, somebody, has been spreading around the link to antpool's priority queue, so people who are cheaping out on their fees can abuse this system to save a couple of bucks
2) ViaBTC's free slots are gone in less than a second... I haven't been able to push a single transaction to their queue today
3) I can still give advice on CPFP, RBF or Double spending... However, do know that this advise is rather technical...

So, from now on, i will only help people to fix their own problem... I will no longer be pushing their transactions to priority queues... I haven't discussed this with HCP (yet), but i do hope he shares the same idear....