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: 35c835e56daa15362bd13576b091637866fc3f4ccff46d5779cfe18ac1a8f21a
Tx prefix hash: 4473ba0f1f75da12ac8405d66adf11d535c52e11a9fa1f9f0e663156751e6a9b
Tx public key: b02416fb734bd3977615128004304ce924a4e98f8dda198628759c049c312cdd
| Timestamp: 1780976953 | Timestamp [UTC]: 2026-06-09 03:49:13 | Age [y:d:h:m:s]: 00:000:04:05:01 |
| Block: 7948 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 302 | RingCT/type: yes/0 |
| Extra: 01b02416fb734bd3977615128004304ce924a4e98f8dda198628759c049c312cdd020900000001e49593ff00 | ||
1 output(s) for total of 34.655079008700 HMNY
| stealth address | amount | amount idx | tag |
| 00: ac89d1ec77dc3675bafce5c770e07ee5d28a363e398f4a2640d1855350384078 | 34.655079008700 | 9856 of 0 | <b6> |
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": 8008,
"vin": [ {
"gen": {
"height": 7948
}
}
],
"vout": [ {
"amount": 34655079008700,
"target": {
"tagged_key": {
"key": "ac89d1ec77dc3675bafce5c770e07ee5d28a363e398f4a2640d1855350384078",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 176, 36, 22, 251, 115, 75, 211, 151, 118, 21, 18, 128, 4, 48, 76, 233, 36, 164, 233, 143, 141, 218, 25, 134, 40, 117, 156, 4, 156, 49, 44, 221, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}