user35800: I'm running a full node without the GUI, so I'm controlling it with bitcoin-cli.
I sent bitcoin to another address, same as I always do, but this time I can't pull up the transaction on any of the block explorers and when I use bitcoin-cli gettransaction ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024, it comes back with:
  "amount": -0.01949732,
  "fee": -0.00007460,
  "confirmations": 0,
  "trusted": false,
  "txid": "ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024",
  "walletconflicts": [
  ],
  "time": 1479664206,
  "timereceived": 1479664206,
  "bip125-replaceable": "unknown"

I've never seen "trusted": false on any other transaction, so I assume that has something to do with it, but I can't find any information online to tell me what it means.
EDIT:
Pasting the hex format of the raw transaction into blockchain.info/pushtx and pushing it that way has set it to trusted: true and now it's showing up. I'd still like to know why it happened and/or how I can fix it myself without relying on blockchain.info's pushtx tool.

user2306: A transaction will be distrusted if

it conflicts with a transaction already in the blockchain, or
it is from someone else, and it is not confirmed.

A transaction will be trusted if

it has confirmations.

If a transaction is not trusted, the client won't create transactions that spend it. (You wouldn't want a transaction you created to be in limbo because one of its inputs wasn't confirmed.)
Once that transaction is confirmed, the trusted field in listtransactions will be true.

35800: <p>I'm running a full node without the GUI, so I'm controlling it with <code>bitcoin-cli</code>.</p>

<p>I sent bitcoin to another address, same as I always do, but this time I can't pull up the transaction on any of the block explorers and when I use <code>bitcoin-cli gettransaction ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024</code>, it comes back with:</p>

<pre><code>  "amount": -0.01949732,
  "fee": -0.00007460,
  "confirmations": 0,
  "trusted": false,
  "txid": "ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024",
  "walletconflicts": [
  ],
  "time": 1479664206,
  "timereceived": 1479664206,
  "bip125-replaceable": "unknown"
</code></pre>

<p>I've never seen <code>"trusted": false</code> on any other transaction, so I assume that has something to do with it, but I can't find any information online to tell me what it means.</p>

<p><strong>EDIT:</strong>
Pasting the hex format of the raw transaction into blockchain.info/pushtx and pushing it that way has set it to <code>trusted: true</code> and now it's showing up. I'd still like to know why it happened and/or how I can fix it myself without relying on blockchain.info's pushtx tool.</p>
 2306: <p>A transaction will be distrusted if</p>

<ul>
<li>it conflicts with a transaction already in the blockchain, or</li>
<li>it is from someone else, and it is not confirmed.</li>
</ul>

<p>A transaction will be trusted if</p>

<ul>
<li>it has confirmations.</li>
</ul>

<p>If a transaction is not trusted, the client won't create transactions that spend it. (You wouldn't want a transaction you created to be in limbo because one of its inputs wasn't confirmed.)</p>

<p>Once that transaction is confirmed, the trusted field in <code>listtransactions</code> will be true.</p>
