For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: d4b671440e9bdaa0a10066b3f668cfb30ec17f5c30c0fd5de9dc9c2fefa886e1
Tx prefix hash: e6a7d55e197d8cab7c82f7ce161e6363fbb967247c8ab5806996665fa037a2cc
Tx public key: a85e4723fd0dea966aeb1dcc1eddccbd6bba93dc5713caa565c0343bb0269b36
| Timestamp: 1779805692 | Timestamp [UTC]: 2026-05-26 14:28:12 | Age [y:d:h:m:s]: 00:013:10:18:35 |
| Block: 2347 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5539 | RingCT/type: yes/0 |
| Extra: 01a85e4723fd0dea966aeb1dcc1eddccbd6bba93dc5713caa565c0343bb0269b3602090000000426697be300 | ||
1 output(s) for total of 35.033889857559 HMNY
| stealth address | amount | amount idx | tag |
| 00: d5e9399e219b34bf28da806f7604bfdd22599d4755d0fe36bd16d67a302633ef | 35.033889857559 | 2747 of 0 | <48> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 2407,
"vin": [ {
"gen": {
"height": 2347
}
}
],
"vout": [ {
"amount": 35033889857559,
"target": {
"tagged_key": {
"key": "d5e9399e219b34bf28da806f7604bfdd22599d4755d0fe36bd16d67a302633ef",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 168, 94, 71, 35, 253, 13, 234, 150, 106, 235, 29, 204, 30, 221, 204, 189, 107, 186, 147, 220, 87, 19, 202, 165, 101, 192, 52, 59, 176, 38, 155, 54, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}