In my test case there were a bunch (like 20) of this kind:
{
"txid" : "135d239f677d220568709f0f3c5b8db220eaf073bd806db02532da3fccb48a35",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "cc0f5acac12049426e60fcaa6b245ba444e378caaf4b50289f2daeb04ac6bc93",
"vout" : 0,
"scriptSig" : {
"asm" : "3045022100c26d8b48e63da9aa6789d887c864ff7ca44483149310e96784a95a5ce5c575850220218c9f37e6e556ab019ddd645441576677f78c180b4388925a674e8f05461b9c01 032c33c149731bcb11ecd2f3e93c765da41b8885d087b2aafb50b3fa75d0a5a641",
"hex" : "483045022100c26d8b48e63da9aa6789d887c864ff7ca44483149310e96784a95a5ce5c575850220218c9f37e6e556ab019ddd645441576677f78c180b4388925a674e8f05461b9c0121032c33c149731bcb11ecd2f3e93c765da41b8885d087b2aafb50b3fa75d0a5a641"
},


and just one with the other kind (i.e. with address and amount like in your bolded example).

So the address is of the receiver.

Thanks

Quote from: tonyk on June 19, 2014, 07:37:40 PM

Quote from: testz on June 19, 2014, 12:25:34 PM

Quote from: tonyk on June 19, 2014, 11:55:54 AM
I was back here to explain why it is hard to believe the client does not store that info and I see that it does.

Thanks.

This is a question?  :)

There was no question there, but actually I have follow up question:

From the result of decoderawtransaction <hex string>
How do I figure out:
-sender
-receiver
-amount

I'm not sure where sender, but I mark as bold receivers and amounts.

decoderawtransaction 010000000193bcc64ab0ae2d9f28504bafca78e344a45b246baafc606e424920c1ca5a0fcc000000006b483045022100c26d8b48e63da9aa6789d887c864ff7ca44483149310e96784a95a5ce5c575850220218c9f37e6e556ab019ddd645441576677f78c180b4388925a674e8f05461b9c0121032c33c149731bcb11ecd2f3e93c765da41b8885d087b2aafb50b3fa75d0a5a641ffffffff0200c2eb0b000000001976a9143745ff24efa9ece32719711caca954fc039fb0fe88ac60c6ee03000000001976a914ba6f1afd6be25d69e98e584cbcdaca7e3d5556e488ac00000000

{
"txid" : "135d239f677d220568709f0f3c5b8db220eaf073bd806db02532da3fccb48a35",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "cc0f5acac12049426e60fcaa6b245ba444e378caaf4b50289f2daeb04ac6bc93",
"vout" : 0,
"scriptSig" : {
"asm" : "3045022100c26d8b48e63da9aa6789d887c864ff7ca44483149310e96784a95a5ce5c575850220218c9f37e6e556ab019ddd645441576677f78c180b4388925a674e8f05461b9c01 032c33c149731bcb11ecd2f3e93c765da41b8885d087b2aafb50b3fa75d0a5a641",
"hex" : "483045022100c26d8b48e63da9aa6789d887c864ff7ca44483149310e96784a95a5ce5c575850220218c9f37e6e556ab019ddd645441576677f78c180b4388925a674e8f05461b9c0121032c33c149731bcb11ecd2f3e93c765da41b8885d087b2aafb50b3fa75d0a5a641"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 2.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 3745ff24efa9ece32719711caca954fc039fb0fe OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a9143745ff24efa9ece32719711caca954fc039fb0fe88ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"Pcy3A5uYKRu5e5jAxfT1QXAFmLfG4ML5s2"
]
}
},
{
"value" : 0.65980000,
"n" : 1,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 ba6f1afd6be25d69e98e584cbcdaca7e3d5556e4 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914ba6f1afd6be25d69e98e584cbcdaca7e3d5556e488ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"PpvYvW7UcDuHkEEBCLahr2nDgGdpbvZRxX"
]
}
}
]
}

Quote from: testz on June 19, 2014, 12:25:34 PM

Quote from: tonyk on June 19, 2014, 11:55:54 AM
I was back here to explain why it is hard to believe the client does not store that info and I see that it does.

Thanks.

This is a question?  :)

There was no question there, but actually I have follow up question:

From the result of decoderawtransaction <hex string>
How do I figure out:
-sender
-receiver
-amount

Quote from: tonyk on June 19, 2014, 11:55:54 AM
I was back here to explain why it is hard to believe the client does not store that info and I see that it does.

Thanks.

This is a question?  :)

Quote from: testz on June 19, 2014, 04:34:18 AM

Quote from: tonyk on June 18, 2014, 11:29:33 PM
If anybody else cares:

I was told, by reputable source, that what I asked for is not possible through the client.

It's not simple but possible, you can get transaction from memory pool by commands:

Code Select Expand


getrawmempool
getrawtransaction <txid>
decoderawtransaction <hex string>


I was back here to explain why it is hard to believe the client does not store that info and I see that it does.

Thanks.

Quote from: testz on June 19, 2014, 04:34:18 AM

Quote from: tonyk on June 18, 2014, 11:29:33 PM
If anybody else cares:

I was told, by reputable source, that what I asked for is not possible through the client.

It's not simple but possible, you can get transaction from memory pool by commands:

Code Select Expand


getrawmempool
getrawtransaction <txid>
decoderawtransaction <hex string>


Wow, learn something new every day

Quote from: tonyk on June 18, 2014, 11:29:33 PM
If anybody else cares:

I was told, by reputable source, that what I asked for is not possible through the client.

It's not simple but possible, you can get transaction from memory pool by commands:

getrawmempool
getrawtransaction <txid>
decoderawtransaction <hex string>


If anybody else cares:

I was told, by reputable source, that what I asked for is not possible through the client.

Actually this lists my transactions.

I am trying to see the transactions my wallet knows about but they are not in a block yet.

[EDIT]Typing slow ...

Hmm .. but that only shows transactions that concern your addresses ... afair there is a parameter "txindex" which can somehow be used for all txs .. but i have no clue

OK that worked thanks

Oh .. in pts you can use
listtransactions

Thanks! but Method not found
It's PTS question

Blockchain_get_pending_transactions

PTS/ protoshares-qt; Windows question

How do you see all (not just yours) unconfirmed (transmitted but not included in a block) transactions?

Thanks.