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: 74292c13e344f1478513a794d28fb5eed5b86a5fa1f67c83194ba59b35b42915
Tx prefix hash: a11715cc776b15311a06ca5076e7c301a041d211e24bb890e4c21b5602199e80
Tx public key: 1c30d8cbbcc7db523bcc23cd079f020d4c849b5aa48558da992cf65eadbed31d
| Timestamp: 1780314592 | Timestamp [UTC]: 2026-06-01 11:49:52 | Age [y:d:h:m:s]: 00:007:14:59:56 |
| Block: 4994 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2906 | RingCT/type: yes/0 |
| Extra: 011c30d8cbbcc7db523bcc23cd079f020d4c849b5aa48558da992cf65eadbed31d02090000000626697be300 | ||
1 output(s) for total of 34.853504884710 HMNY
| stealth address | amount | amount idx | tag |
| 00: 792206866ead0830207f2b2d409bf6d7e120c2a2502ce50fbf2a1e81d6416982 | 34.853504884710 | 6359 of 0 | <f5> |
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": 5054,
"vin": [ {
"gen": {
"height": 4994
}
}
],
"vout": [ {
"amount": 34853504884710,
"target": {
"tagged_key": {
"key": "792206866ead0830207f2b2d409bf6d7e120c2a2502ce50fbf2a1e81d6416982",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 28, 48, 216, 203, 188, 199, 219, 82, 59, 204, 35, 205, 7, 159, 2, 13, 76, 132, 155, 90, 164, 133, 88, 218, 153, 44, 246, 94, 173, 190, 211, 29, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}