about unconfirmed transaction

[o_e_l_e_o]

These rebroadcasting services can only rebroadcast a transaction from its transaction ID if they have the transaction in their mempool already. From searching for his second transaction, I cannot find it in any mempool. If he wants to broadcast it, he'll need a copy of of full transaction. You cannot broadcast a transaction from scratch using just the transaction ID.

[NeuroticFish]

These rebroadcasting services can only rebroadcast a transaction from its transaction ID if they have the transaction in their mempool already.

This is obvious.

From searching for his second transaction, I cannot find it in any mempool.

I thought that you talk about fe682ab28ecdb3bc82498af0c7730e2fcb0cf8563c6fc88cc2367c16aa3624a0
I've checked more and I guess that you were talking about b405185bc699d24a611cb25aeb3347159235c968bbb0d58a8c98cc1b96cd6ccf which indeed is rara avis.
But I can always rely on chain.so to find such transactions and again it doesn't disappoint  

Is the hex tx from here enough for re-broadcasting it?

Edit: I've re-broadcasted it, the hex tx worked with coinb.in

[o_e_l_e_o]

Well found. I also just rebroadcast it on blockchair.com, and it is showing up there currently.

Having a quick look at the parents, the issue with this transaction is the same as the other one. Although this transaction pays 151 sats/vbyte, I've found an unconfirmed parent with 907 inputs, which is 82,292 vbytes and only pays a fee of 3 sats/vbyte.

Whoever is making these transactions has picked a very bad time to try to consolidate their inputs.