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: 97a3c8843dad28049b754e1a2a841c5b49eb1ce0e88ab206ac1e710db6bdd152
Tx prefix hash: e5f9f0388d400c5f66ca9cb5b36b3e873d969a74e32a6ed62bb265e0346179c0
Tx public key: 1f98674ec4e58207253285a87911b20d98ecd8e4f92047cacb0e34b120487dc3
| Timestamp: 1781005106 | Timestamp [UTC]: 2026-06-09 11:38:26 | Age [y:d:h:m:s]: 00:006:05:04:48 |
| Block: 8523 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 222 | RingCT/type: yes/0 |
| Extra: 011f98674ec4e58207253285a87911b20d98ecd8e4f92047cacb0e34b120487dc3020900000002e49593ff00 | ||
1 output(s) for total of 34.617092698956 HMNY
| stealth address | amount | amount idx | tag |
| 00: 14fc151a09179d9dfcbf535190d3aa11a2c83c59c8eaf58cf18fc70ddfd15353 | 34.617092698956 | 10527 of 0 | <51> |
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": 8583,
"vin": [ {
"gen": {
"height": 8523
}
}
],
"vout": [ {
"amount": 34617092698956,
"target": {
"tagged_key": {
"key": "14fc151a09179d9dfcbf535190d3aa11a2c83c59c8eaf58cf18fc70ddfd15353",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 31, 152, 103, 78, 196, 229, 130, 7, 37, 50, 133, 168, 121, 17, 178, 13, 152, 236, 216, 228, 249, 32, 71, 202, 203, 14, 52, 177, 32, 72, 125, 195, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}