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: 70e05eef41e28d243013427a6d322d5192bfe42d7433b807fd6829044735e40f
Tx prefix hash: e152f5c34030e3ea4f5580e31d9888ce4c25ea0c1740e400600b94bd8ebd43f6
Tx public key: f471176153ca3f8cffba4fd343ae115ae4fe34c32efe405b2a9476280e412861
| Timestamp: 1780697992 | Timestamp [UTC]: 2026-06-05 22:19:52 | Age [y:d:h:m:s]: 00:003:02:26:55 |
| Block: 6019 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1867 | RingCT/type: yes/0 |
| Extra: 01f471176153ca3f8cffba4fd343ae115ae4fe34c32efe405b2a9476280e412861020900000003e49593ff00 | ||
1 output(s) for total of 34.782819566360 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4da3e576042860cd9a59eda77225363bb763da96dcb3ee08d8d5c2731a2b218f | 34.782819566360 | 7486 of 0 | <5e> |
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": 6079,
"vin": [ {
"gen": {
"height": 6019
}
}
],
"vout": [ {
"amount": 34782819566360,
"target": {
"tagged_key": {
"key": "4da3e576042860cd9a59eda77225363bb763da96dcb3ee08d8d5c2731a2b218f",
"view_tag": "5e"
}
}
}
],
"extra": [ 1, 244, 113, 23, 97, 83, 202, 63, 140, 255, 186, 79, 211, 67, 174, 17, 90, 228, 254, 52, 195, 46, 254, 64, 91, 42, 148, 118, 40, 14, 65, 40, 97, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}