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: 872a45bf1a59a163e6ae8d5d5cb2aea0d4b7a823cdf482aed1fd9c5c2558d525
Tx prefix hash: 46c24cafbf417a3c5ad6706fdb8bf22d37bd7b0b4ee7b2c3fcc390d32f788bf0
Tx public key: 0337acde4915fafe4a9623844544e7d845214987323498a16aac8ea586e9f9bc
| Timestamp: 1780388952 | Timestamp [UTC]: 2026-06-02 08:29:12 | Age [y:d:h:m:s]: 00:006:19:21:46 |
| Block: 5193 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2799 | RingCT/type: yes/0 |
| Extra: 010337acde4915fafe4a9623844544e7d845214987323498a16aac8ea586e9f9bc02090000000126697be300 | ||
1 output(s) for total of 34.837662096421 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9df6db85ac59b7d04279ffd3356586f0f4ae2ff1d0f28e4eb19ec9beaa6dce27 | 34.837662096421 | 6574 of 0 | <82> |
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": 5253,
"vin": [ {
"gen": {
"height": 5193
}
}
],
"vout": [ {
"amount": 34837662096421,
"target": {
"tagged_key": {
"key": "9df6db85ac59b7d04279ffd3356586f0f4ae2ff1d0f28e4eb19ec9beaa6dce27",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 3, 55, 172, 222, 73, 21, 250, 254, 74, 150, 35, 132, 69, 68, 231, 216, 69, 33, 73, 135, 50, 52, 152, 161, 106, 172, 142, 165, 134, 233, 249, 188, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}