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: 0ef482c2de3ecb867eb0e3fa75536dfbc9dd3498fa85493e4716c006508c4ed5
Tx prefix hash: a7a3b3df3925adb86a93b93c752380bddd24f8c7065d0671281302439c414b4b
Tx public key: 09660315054b7b04340049fb102ca1e90d83b90eee5b3cd2c3cf334a2ccb5913
| Timestamp: 1779434977 | Timestamp [UTC]: 2026-05-22 07:29:37 | Age [y:d:h:m:s]: 00:022:03:32:39 |
| Block: 111 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8634 | RingCT/type: yes/0 |
| Extra: 0109660315054b7b04340049fb102ca1e90d83b90eee5b3cd2c3cf334a2ccb5913020900000001a662ed0300 | ||
1 output(s) for total of 35.176990881213 HMNY
| stealth address | amount | amount idx | tag |
| 00: d34e39fe8a981da9518157eb4858b680d75ac5de2c51db5cd7563cfe7fa1bbe9 | 35.176990881213 | 107 of 0 | <46> |
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": 171,
"vin": [ {
"gen": {
"height": 111
}
}
],
"vout": [ {
"amount": 35176990881213,
"target": {
"tagged_key": {
"key": "d34e39fe8a981da9518157eb4858b680d75ac5de2c51db5cd7563cfe7fa1bbe9",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 9, 102, 3, 21, 5, 75, 123, 4, 52, 0, 73, 251, 16, 44, 161, 233, 13, 131, 185, 14, 238, 91, 60, 210, 195, 207, 51, 74, 44, 203, 89, 19, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}