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: 8c24a04066e20a39e382b4c2b8feb737d549b4863bc5ad15e078ce26d7f9b8a4
Tx prefix hash: fb50e53c9b130488400737915e4c7ab014e5c9ebe875e7ebade6e132c92b4c32
Tx public key: 2ed524b7e4f4911852c90d36498c17d0c402c48c7e05737f6f985d8494e503c4
| Timestamp: 1780694057 | Timestamp [UTC]: 2026-06-05 21:14:17 | Age [y:d:h:m:s]: 00:003:06:24:33 |
| Block: 5914 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2032 | RingCT/type: yes/0 |
| Extra: 012ed524b7e4f4911852c90d36498c17d0c402c48c7e05737f6f985d8494e503c4020900000001e49593ff00 | ||
1 output(s) for total of 34.789786281750 HMNY
| stealth address | amount | amount idx | tag |
| 00: be3db0610811828a605d3168c062cd28df7ad674924161ec2c02d7ebad77e374 | 34.789786281750 | 7375 of 0 | <1d> |
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": 5974,
"vin": [ {
"gen": {
"height": 5914
}
}
],
"vout": [ {
"amount": 34789786281750,
"target": {
"tagged_key": {
"key": "be3db0610811828a605d3168c062cd28df7ad674924161ec2c02d7ebad77e374",
"view_tag": "1d"
}
}
}
],
"extra": [ 1, 46, 213, 36, 183, 228, 244, 145, 24, 82, 201, 13, 54, 73, 140, 23, 208, 196, 2, 196, 140, 126, 5, 115, 127, 111, 152, 93, 132, 148, 229, 3, 196, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}