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: b9398422efac85390b3f03506fc23ec037c120239c75da4804e8ced41d08d67e
Tx prefix hash: efa089eadaee1c8115e11af2bb73fa1748d1a6298bd0c73e1a2d6506d9914cd7
Tx public key: 511036d6f8c88065c449504e312929dbff7b0adb791c0929fa684ae8c9e776bd
| Timestamp: 1779960646 | Timestamp [UTC]: 2026-05-28 09:30:46 | Age [y:d:h:m:s]: 00:011:13:48:07 |
| Block: 3754 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4132 | RingCT/type: yes/0 |
| Extra: 01511036d6f8c88065c449504e312929dbff7b0adb791c0929fa684ae8c9e776bd02090000000226697be300 | ||
1 output(s) for total of 34.933411577372 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2aa399c49bbdd642d1ecb113d92d0a17df334918ddb0eb63ffb41add1fac7a12 | 34.933411577372 | 4552 of 0 | <c9> |
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": 3814,
"vin": [ {
"gen": {
"height": 3754
}
}
],
"vout": [ {
"amount": 34933411577372,
"target": {
"tagged_key": {
"key": "2aa399c49bbdd642d1ecb113d92d0a17df334918ddb0eb63ffb41add1fac7a12",
"view_tag": "c9"
}
}
}
],
"extra": [ 1, 81, 16, 54, 214, 248, 200, 128, 101, 196, 73, 80, 78, 49, 41, 41, 219, 255, 123, 10, 219, 121, 28, 9, 41, 250, 104, 74, 232, 201, 231, 118, 189, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}