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: 4b5f7201807fcbcedea45843214d9f5351c70db335f431fb32d2290b8482d471
Tx prefix hash: 8352329d75cf90291d53d883c44b7c716111f115ca68150fa3d5f3963f75ca67
Tx public key: 237cc470f4c42cd5c1060575971f8a0957cf5c35b9ba5c28078618ab347b216d
| Timestamp: 1780978760 | Timestamp [UTC]: 2026-06-09 04:19:20 | Age [y:d:h:m:s]: 00:000:08:14:07 |
| Block: 7990 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 580 | RingCT/type: yes/0 |
| Extra: 01237cc470f4c42cd5c1060575971f8a0957cf5c35b9ba5c28078618ab347b216d020900000001e49593ff00 | ||
1 output(s) for total of 34.652302945909 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5752171f7595e4c51f12970b5dd9c04d495729d42377c1caec65de975e3a5774 | 34.652302945909 | 9906 of 0 | <fd> |
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": 8050,
"vin": [ {
"gen": {
"height": 7990
}
}
],
"vout": [ {
"amount": 34652302945909,
"target": {
"tagged_key": {
"key": "5752171f7595e4c51f12970b5dd9c04d495729d42377c1caec65de975e3a5774",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 35, 124, 196, 112, 244, 196, 44, 213, 193, 6, 5, 117, 151, 31, 138, 9, 87, 207, 92, 53, 185, 186, 92, 40, 7, 134, 24, 171, 52, 123, 33, 109, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}