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: 4b9570292adc362d6f8a284edf4d18aa238aec9fad5f087f4c4420dedd6e2a4d
Tx prefix hash: 7da18b15bdddb2777cdb0dd1ea2eaa6b5f897518a161ed63526e410f431a7619
Tx public key: 2407a7a02f3cc06b08ba7de3d5a4b73cb45f57062d92a419648e61eb02c14ee4
| Timestamp: 1780977556 | Timestamp [UTC]: 2026-06-09 03:59:16 | Age [y:d:h:m:s]: 00:000:03:54:58 |
| Block: 7956 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 293 | RingCT/type: yes/0 |
| Extra: 012407a7a02f3cc06b08ba7de3d5a4b73cb45f57062d92a419648e61eb02c14ee4020900000001e49593ff00 | ||
1 output(s) for total of 34.654550217689 HMNY
| stealth address | amount | amount idx | tag |
| 00: ea911e94d98bbc1f47b8c24309e40455b8a8c91c3c93713f43e2acd73754f83b | 34.654550217689 | 9868 of 0 | <c4> |
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": 8016,
"vin": [ {
"gen": {
"height": 7956
}
}
],
"vout": [ {
"amount": 34654550217689,
"target": {
"tagged_key": {
"key": "ea911e94d98bbc1f47b8c24309e40455b8a8c91c3c93713f43e2acd73754f83b",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 36, 7, 167, 160, 47, 60, 192, 107, 8, 186, 125, 227, 213, 164, 183, 60, 180, 95, 87, 6, 45, 146, 164, 25, 100, 142, 97, 235, 2, 193, 78, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}