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: 43a9eee65a75dc4460cb2b4161e6e1a7c3bf82e3142eb94d0976f524703c0ed3
Tx prefix hash: e1e1101f72f119b65ed55a4454b8f605f137d95b36f90caea1fd3753cfc7e591
Tx public key: bbb67f7b0b6090e1f0d68b1489b877a7afa5e263bf37cf3966ced0e5c2848f6f
| Timestamp: 1779677748 | Timestamp [UTC]: 2026-05-25 02:55:48 | Age [y:d:h:m:s]: 00:014:21:50:59 |
| Block: 1510 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6376 | RingCT/type: yes/0 |
| Extra: 01bbb67f7b0b6090e1f0d68b1489b877a7afa5e263bf37cf3966ced0e5c2848f6f | ||
1 output(s) for total of 35.083250310339 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf6b78c0a1ead1370a7fb9961aa46e812f67ff145ada1d3a78d45ad7e4ee5f11 | 35.083250310339 | 1666 of 0 | <13> |
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": 1570,
"vin": [ {
"gen": {
"height": 1510
}
}
],
"vout": [ {
"amount": 35083250310339,
"target": {
"tagged_key": {
"key": "cf6b78c0a1ead1370a7fb9961aa46e812f67ff145ada1d3a78d45ad7e4ee5f11",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 187, 182, 127, 123, 11, 96, 144, 225, 240, 214, 139, 20, 137, 184, 119, 167, 175, 165, 226, 99, 191, 55, 207, 57, 102, 206, 208, 229, 194, 132, 143, 111
],
"rct_signatures": {
"type": 0
}
}