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: 3a5f916f213d5e65479d74b7b3634c1b4e2ecf9efd96fff8649e2f6fbdf1eaf7
Tx prefix hash: 69729b2252d1606f16c8afc54035810e5afe489f7580a47a2fa7db3f35d16b90
Tx public key: b88b9e1ed39f5f063e330d3275f30d159a1e6f4bbbe5d4718fe29004f1a79a8d
| Timestamp: 1779435646 | Timestamp [UTC]: 2026-05-22 07:40:46 | Age [y:d:h:m:s]: 00:022:03:21:30 |
| Block: 124 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8621 | RingCT/type: yes/0 |
| Extra: 01b88b9e1ed39f5f063e330d3275f30d159a1e6f4bbbe5d4718fe29004f1a79a8d020900000001a662ed0300 | ||
1 output(s) for total of 35.176118658983 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9b997ddee7e742af2219d20caa8812bd7c23256615bc166326dc5412a3bfd6c7 | 35.176118658983 | 120 of 0 | <27> |
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": 184,
"vin": [ {
"gen": {
"height": 124
}
}
],
"vout": [ {
"amount": 35176118658983,
"target": {
"tagged_key": {
"key": "9b997ddee7e742af2219d20caa8812bd7c23256615bc166326dc5412a3bfd6c7",
"view_tag": "27"
}
}
}
],
"extra": [ 1, 184, 139, 158, 30, 211, 159, 95, 6, 62, 51, 13, 50, 117, 243, 13, 21, 154, 30, 111, 75, 187, 229, 212, 113, 143, 226, 144, 4, 241, 167, 154, 141, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}