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: 419027a846807e4730b2946582a62c8d493effce870d40128e8018c640ba94c5
Tx prefix hash: 3c567e85d23a9cad54bb654ee778e18b6455c46bea67d78732ee7dfc3cac92d5
Tx public key: 78ac284cccbc56eb2f437fbbad0ad4bea0a9d2882fabcd46828abff25d422d70
| Timestamp: 1780323191 | Timestamp [UTC]: 2026-06-01 14:13:11 | Age [y:d:h:m:s]: 00:007:10:33:36 |
| Block: 5074 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2812 | RingCT/type: yes/0 |
| Extra: 0178ac284cccbc56eb2f437fbbad0ad4bea0a9d2882fabcd46828abff25d422d7002090000000426697be300 | ||
1 output(s) for total of 34.845570261898 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6aa1aa542208297c62a60c3f77609f8a608e4dda72d407412cf131ba21e0422a | 34.845570261898 | 6449 of 0 | <a1> |
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": 5134,
"vin": [ {
"gen": {
"height": 5074
}
}
],
"vout": [ {
"amount": 34845570261898,
"target": {
"tagged_key": {
"key": "6aa1aa542208297c62a60c3f77609f8a608e4dda72d407412cf131ba21e0422a",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 120, 172, 40, 76, 204, 188, 86, 235, 47, 67, 127, 187, 173, 10, 212, 190, 160, 169, 210, 136, 47, 171, 205, 70, 130, 138, 191, 242, 93, 66, 45, 112, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}