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: 65445b0bc9ce5d0a3040af6fa61f045dc196d67965723872f7c2bc0386be2cf6
Tx prefix hash: 08b58675cea6905d926f4e0b2534a916d891e0c12a0d6d9379677bf6353374e9
Tx public key: 3b6e9d7841a6e010adf9400a93d83ba996a8c5309407900e4722132497d8716b
| Timestamp: 1779885083 | Timestamp [UTC]: 2026-05-27 12:31:23 | Age [y:d:h:m:s]: 00:012:12:15:24 |
| Block: 3002 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4884 | RingCT/type: yes/0 |
| Extra: 013b6e9d7841a6e010adf9400a93d83ba996a8c5309407900e4722132497d8716b02090000000126697be300 | ||
1 output(s) for total of 34.983553483017 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b5786f0f2edb55cb6982b772ff298844153a94d05bc0310f9addcf4aa85677a | 34.983553483017 | 3564 of 0 | <5c> |
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": 3062,
"vin": [ {
"gen": {
"height": 3002
}
}
],
"vout": [ {
"amount": 34983553483017,
"target": {
"tagged_key": {
"key": "3b5786f0f2edb55cb6982b772ff298844153a94d05bc0310f9addcf4aa85677a",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 59, 110, 157, 120, 65, 166, 224, 16, 173, 249, 64, 10, 147, 216, 59, 169, 150, 168, 197, 48, 148, 7, 144, 14, 71, 34, 19, 36, 151, 216, 113, 107, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}