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: b2f2b1fd877adb8e9747c3b0b1c0e09d684f31a504819ea73af8d5ae940571a1
Tx prefix hash: 0a3f44ba08aed03d6de619c3c3a76f7a4da7019b7fd47c67e311b061747e7ed0
Tx public key: 8d09fd7205d94d8a9fd5613bebfe4a1148000d215e0b9d04ce8cf8b178d51f61
| Timestamp: 1779629511 | Timestamp [UTC]: 2026-05-24 13:31:51 | Age [y:d:h:m:s]: 00:015:12:04:06 |
| Block: 836 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7050 | RingCT/type: yes/0 |
| Extra: 018d09fd7205d94d8a9fd5613bebfe4a1148000d215e0b9d04ce8cf8b178d51f61020900000001ba6d17be00 | ||
1 output(s) for total of 35.128380732870 HMNY
| stealth address | amount | amount idx | tag |
| 00: e439e4fe554354eea6984a48f35a7cb911ce13929f02f30b10b8287a6c807bb7 | 35.128380732870 | 968 of 0 | <4c> |
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": 896,
"vin": [ {
"gen": {
"height": 836
}
}
],
"vout": [ {
"amount": 35128380732870,
"target": {
"tagged_key": {
"key": "e439e4fe554354eea6984a48f35a7cb911ce13929f02f30b10b8287a6c807bb7",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 141, 9, 253, 114, 5, 217, 77, 138, 159, 213, 97, 59, 235, 254, 74, 17, 72, 0, 13, 33, 94, 11, 157, 4, 206, 140, 248, 177, 120, 213, 31, 97, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}