BitShares Forum
Main => Technical Support => Topic started by: hybridd on November 08, 2015, 03:50:37 pm
-
{
"ref_block_num": 43551,
"ref_block_prefix": 4241440461,
"expiration": "2015-11-04T19:39:45",
"operations": [
[
0,
{
"fee": {
"amount": 4000000,
"asset_id": "1.3.0"
},
"from": "1.2.96505",
"to": "1.2.93813",
"amount": {
"amount": 5000000,
"asset_id": "1.3.0"
},
"extensions": []
}
]
],
"extensions": [],
"signatures": [
"1f0e157e5c1c14c0bc0a6294e841b3b1f97fb905203fa5ec7f6e12b4e154600fed512432219e69d034c96e3eb1a9b8f8e1e72158fd9fb4f12ecfe97fb8e413768e"
]
}
Looking at a site like, http://cryptofresh.com/b/742530 there seems to be a clear distinction between a "signature" and a "transaction id" so I'm not 100% sure that a signature is the transaction id? Not sure, slightly confused about this... would appreciate if someone could enlighten me.
-
Yeah, this part of the API is very confusing.. the most useful part is "transaction_ids" array of the block object.
But afaik there's no API call to retrieve a tx by its transaction_id. I had to build my own index and it's accessible like so:
http://cryptofresh.com/tx/b546a75a891b5c51de6d1aafd40d10e91a717bb3
Relevant discussion:
https://bitsharestalk.org/index.php/topic,19527.0.html
-
What data can be used to retrieve a transaction then in the transfer response, it's signature?
-
Use the new transfer2 api
-
cheers, this indeed does solve my problem as transfer2 returns the tx id... I didn't look properly at its implementation, thanks guys!