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: c978128650c0d150bb558d0967d6fab2e8e77f60d99e90c0b8d3776d03e5e4dd
Tx prefix hash: 7f3dd619cb5e2b6a8a4d936a57d073722445372b7cbe6c1cfd706af9bb7e6e84
Tx public key: c6ba8b990e41aeb9dcf7abefc0e5ea36aa75a5b36a81e6e212446a89b09147b3
| Timestamp: 1779723221 | Timestamp [UTC]: 2026-05-25 15:33:41 | Age [y:d:h:m:s]: 00:014:10:02:16 |
| Block: 1795 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6091 | RingCT/type: yes/0 |
| Extra: 01c6ba8b990e41aeb9dcf7abefc0e5ea36aa75a5b36a81e6e212446a89b09147b3020900000004ba6d17be00 | ||
1 output(s) for total of 35.064184417670 HMNY
| stealth address | amount | amount idx | tag |
| 00: 08ed4736b13357f553ab78b81d6155e8376ef92082c05a72ec7a1b7f463d84c8 | 35.064184417670 | 1984 of 0 | <9d> |
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": 1855,
"vin": [ {
"gen": {
"height": 1795
}
}
],
"vout": [ {
"amount": 35064184417670,
"target": {
"tagged_key": {
"key": "08ed4736b13357f553ab78b81d6155e8376ef92082c05a72ec7a1b7f463d84c8",
"view_tag": "9d"
}
}
}
],
"extra": [ 1, 198, 186, 139, 153, 14, 65, 174, 185, 220, 247, 171, 239, 192, 229, 234, 54, 170, 117, 165, 179, 106, 129, 230, 226, 18, 68, 106, 137, 176, 145, 71, 179, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}