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: 19e716f50f42a20dad1172a2b3457c91d77ae3c37aa5aabad50825f35df45c0e
Tx prefix hash: 82b016a750dbb4c14b06112f15f1338bee1c999002e227c53e3b562d83f33e73
Tx public key: 96bb53391c6bad3425b91bafff6558c453ebafe7c8153dbc33215e26b13b3a70
| Timestamp: 1780862535 | Timestamp [UTC]: 2026-06-07 20:02:15 | Age [y:d:h:m:s]: 00:001:02:22:34 |
| Block: 7633 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 253 | RingCT/type: yes/0 |
| Extra: 0196bb53391c6bad3425b91bafff6558c453ebafe7c8153dbc33215e26b13b3a70020900000001e49593ff00 | ||
1 output(s) for total of 34.675906569723 HMNY
| stealth address | amount | amount idx | tag |
| 00: f2067201acd95f38180feef9ee289a87fd434ffefca509976d580ccf3f09a4d1 | 34.675906569723 | 9435 of 0 | <2e> |
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": 7693,
"vin": [ {
"gen": {
"height": 7633
}
}
],
"vout": [ {
"amount": 34675906569723,
"target": {
"tagged_key": {
"key": "f2067201acd95f38180feef9ee289a87fd434ffefca509976d580ccf3f09a4d1",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 150, 187, 83, 57, 28, 107, 173, 52, 37, 185, 27, 175, 255, 101, 88, 196, 83, 235, 175, 231, 200, 21, 61, 188, 51, 33, 94, 38, 177, 59, 58, 112, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}