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: c07b3b02e2ba9e06f87225d5635804bdac064cf03c76be45472bdce52dd39bdc
Tx prefix hash: de360a062ce5ed695c25cc020f4f99c151e135e585e8d24dcde71d58d686c3aa
Tx public key: 353dc8736d5fe069184c9a7866edac38ab4638c7275572a41918c79d541a18ee
| Timestamp: 1779454033 | Timestamp [UTC]: 2026-05-22 12:47:13 | Age [y:d:h:m:s]: 00:017:12:48:44 |
| Block: 362 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7524 | RingCT/type: yes/0 |
| Extra: 01353dc8736d5fe069184c9a7866edac38ab4638c7275572a41918c79d541a18ee02090000000693369e7d00 | ||
1 output(s) for total of 35.160154104583 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30262811b5f9a493b3cb4b334a574b8b4d67633418c559482dd6374995c23be9 | 35.160154104583 | 358 of 0 | <7b> |
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": 422,
"vin": [ {
"gen": {
"height": 362
}
}
],
"vout": [ {
"amount": 35160154104583,
"target": {
"tagged_key": {
"key": "30262811b5f9a493b3cb4b334a574b8b4d67633418c559482dd6374995c23be9",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 53, 61, 200, 115, 109, 95, 224, 105, 24, 76, 154, 120, 102, 237, 172, 56, 171, 70, 56, 199, 39, 85, 114, 164, 25, 24, 199, 157, 84, 26, 24, 238, 2, 9, 0, 0, 0, 6, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}