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: c3201ff0bec45333b3ce146eb5c84778e7ba464fe3104670d4f17cf817b95a1f
Tx prefix hash: 2ee02113f8cee8d4876be60d8b1fa8671ab755afb87c830f73eff291d3dca9d9
Tx public key: 51b3f36d630b291b6a3e586e82e4d5ea54444d426cb786ac071cb50ce3d069e1
| Timestamp: 1779712902 | Timestamp [UTC]: 2026-05-25 12:41:42 | Age [y:d:h:m:s]: 00:014:12:54:15 |
| Block: 1590 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6296 | RingCT/type: yes/0 |
| Extra: 0151b3f36d630b291b6a3e586e82e4d5ea54444d426cb786ac071cb50ce3d069e1020900000001ba6d17be00 | ||
1 output(s) for total of 35.077897434475 HMNY
| stealth address | amount | amount idx | tag |
| 00: 746e1efe02ca53b247e88392e269d1dc6b009ff306183149f51ddc69b5985309 | 35.077897434475 | 1748 of 0 | <62> |
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": 1650,
"vin": [ {
"gen": {
"height": 1590
}
}
],
"vout": [ {
"amount": 35077897434475,
"target": {
"tagged_key": {
"key": "746e1efe02ca53b247e88392e269d1dc6b009ff306183149f51ddc69b5985309",
"view_tag": "62"
}
}
}
],
"extra": [ 1, 81, 179, 243, 109, 99, 11, 41, 27, 106, 62, 88, 110, 130, 228, 213, 234, 84, 68, 77, 66, 108, 183, 134, 172, 7, 28, 181, 12, 227, 208, 105, 225, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}