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: 7206b0670b387f2d34569380c2c92213eb61209e459a22ebb631426f3845d817
Tx prefix hash: 2765b484162161bd0ae3db02db954efc837672c167a6159c005b1d216bfad853
Tx public key: 22ee2c3edc54d1aa1261b1d8a28a9a2cbbcd080253748ed881c2191f713affd1
| Timestamp: 1779881414 | Timestamp [UTC]: 2026-05-27 11:30:14 | Age [y:d:h:m:s]: 00:012:15:19:34 |
| Block: 2945 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4964 | RingCT/type: yes/0 |
| Extra: 0122ee2c3edc54d1aa1261b1d8a28a9a2cbbcd080253748ed881c2191f713affd102090000000126697be300 | ||
1 output(s) for total of 34.994759865877 HMNY
| stealth address | amount | amount idx | tag |
| 00: 917e316f231e6f4ee0c3e51b52fae6ab5bab1f7ed49326152622d6776feaa64a | 34.994759865877 | 3493 of 0 | <95> |
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": 3005,
"vin": [ {
"gen": {
"height": 2945
}
}
],
"vout": [ {
"amount": 34994759865877,
"target": {
"tagged_key": {
"key": "917e316f231e6f4ee0c3e51b52fae6ab5bab1f7ed49326152622d6776feaa64a",
"view_tag": "95"
}
}
}
],
"extra": [ 1, 34, 238, 44, 62, 220, 84, 209, 170, 18, 97, 177, 216, 162, 138, 154, 44, 187, 205, 8, 2, 83, 116, 142, 216, 129, 194, 25, 31, 113, 58, 255, 209, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}