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: 845634ec2f72c40b9d0e46a66a14ae5791d1fbffc1497d8c21f53b1c4cbfaec4
Tx prefix hash: de76aa5fcc81435ac632d8d2980cb840997944b7c00c91297868bbcc930c3707
Tx public key: 05f089b050a789fb5b075b9ddd6e4686112c4bc3b2833e6ae283c0e5288e85c6
| Timestamp: 1780035535 | Timestamp [UTC]: 2026-05-29 06:18:55 | Age [y:d:h:m:s]: 00:010:18:27:52 |
| Block: 4239 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3647 | RingCT/type: yes/0 |
| Extra: 0105f089b050a789fb5b075b9ddd6e4686112c4bc3b2833e6ae283c0e5288e85c602090000000126697be300 | ||
1 output(s) for total of 34.901110844511 HMNY
| stealth address | amount | amount idx | tag |
| 00: 29fd7f955b99decec60b3da7243c0456717829f2c7bbfbf18b24fbcce1622db7 | 34.901110844511 | 5290 of 0 | <76> |
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": 4299,
"vin": [ {
"gen": {
"height": 4239
}
}
],
"vout": [ {
"amount": 34901110844511,
"target": {
"tagged_key": {
"key": "29fd7f955b99decec60b3da7243c0456717829f2c7bbfbf18b24fbcce1622db7",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 5, 240, 137, 176, 80, 167, 137, 251, 91, 7, 91, 157, 221, 110, 70, 134, 17, 44, 75, 195, 178, 131, 62, 106, 226, 131, 192, 229, 40, 142, 133, 198, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}