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: f92194893e4dd27a036efe02fc2fb5177ee9c2387c17377ecb03b0bdb7b3d60d
Tx prefix hash: c317f977341b693c913b979910ce73cf4b0adc7901d7964f9b02519dd3f36fa5
Tx public key: 44abd94eccfa3ed8b7dc8bf30c0556cc5a55e0ceab9df4135c8c3f2fffe06775
| Timestamp: 1779431669 | Timestamp [UTC]: 2026-05-22 06:34:29 | Age [y:d:h:m:s]: 00:017:15:50:20 |
| Block: 26 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 7860 | RingCT/type: yes/0 |
| Extra: 0144abd94eccfa3ed8b7dc8bf30c0556cc5a55e0ceab9df4135c8c3f2fffe06775 | ||
1 output(s) for total of 35.182694405745 HMNY
| stealth address | amount | amount idx | tag |
| 00: 736844fd37bacf61af1e650d000dbe013fb17e7eff6f9244a8ff8dbc50c21200 | 35.182694405745 | 22 of 0 | <50> |
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": 86,
"vin": [ {
"gen": {
"height": 26
}
}
],
"vout": [ {
"amount": 35182694405745,
"target": {
"tagged_key": {
"key": "736844fd37bacf61af1e650d000dbe013fb17e7eff6f9244a8ff8dbc50c21200",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 68, 171, 217, 78, 204, 250, 62, 216, 183, 220, 139, 243, 12, 5, 86, 204, 90, 85, 224, 206, 171, 157, 244, 19, 92, 140, 63, 47, 255, 224, 103, 117
],
"rct_signatures": {
"type": 0
}
}