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: 837aa4170b0ca555166aca00f93c12396f00186731f3cf57d55a1c88c10b2941
Tx prefix hash: a0e417adcf66c63ba76378c76cd80e496ad8434002b6c4fbe6412f75cc9930ac
Tx public key: d4fe1e9098ef88df11c8a083546e20b7029b99031a71be617e994932ec7cb54b
| Timestamp: 1780761889 | Timestamp [UTC]: 2026-06-06 16:04:49 | Age [y:d:h:m:s]: 00:002:10:44:59 |
| Block: 6578 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1322 | RingCT/type: yes/0 |
| Extra: 01d4fe1e9098ef88df11c8a083546e20b7029b99031a71be617e994932ec7cb54b020900000001e49593ff00 | ||
1 output(s) for total of 34.745753578037 HMNY
| stealth address | amount | amount idx | tag |
| 00: 69d205019480406a0e953cf537ced98df3b10a7c7571b2cbb0e5c2c375e9958f | 34.745753578037 | 8102 of 0 | <0a> |
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": 6638,
"vin": [ {
"gen": {
"height": 6578
}
}
],
"vout": [ {
"amount": 34745753578037,
"target": {
"tagged_key": {
"key": "69d205019480406a0e953cf537ced98df3b10a7c7571b2cbb0e5c2c375e9958f",
"view_tag": "0a"
}
}
}
],
"extra": [ 1, 212, 254, 30, 144, 152, 239, 136, 223, 17, 200, 160, 131, 84, 110, 32, 183, 2, 155, 153, 3, 26, 113, 190, 97, 126, 153, 73, 50, 236, 124, 181, 75, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}