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: e5bcac1a2c6de761c8d921c4e2ab60ad0a48ae491ad8e5b37940f5673ad3e3aa
Tx prefix hash: 903ace68e3f805e8656eefe85a93c0451ab2994f49c8f54bde9c84428284f39a
Tx public key: 7bc19e7de6761c471e0d604f9976d6d68710babe975a46a2877a25bef80384a4
| Timestamp: 1780706138 | Timestamp [UTC]: 2026-06-06 00:35:38 | Age [y:d:h:m:s]: 00:002:22:43:15 |
| Block: 6111 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1775 | RingCT/type: yes/0 |
| Extra: 017bc19e7de6761c471e0d604f9976d6d68710babe975a46a2877a25bef80384a4020900000001e49593ff00 | ||
1 output(s) for total of 34.776716543395 HMNY
| stealth address | amount | amount idx | tag |
| 00: acfef7263aed09c536ef3184d8c7fd282ba912d68eb011bdcf2bec7b74729a11 | 34.776716543395 | 7584 of 0 | <30> |
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": 6171,
"vin": [ {
"gen": {
"height": 6111
}
}
],
"vout": [ {
"amount": 34776716543395,
"target": {
"tagged_key": {
"key": "acfef7263aed09c536ef3184d8c7fd282ba912d68eb011bdcf2bec7b74729a11",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 123, 193, 158, 125, 230, 118, 28, 71, 30, 13, 96, 79, 153, 118, 214, 214, 135, 16, 186, 190, 151, 90, 70, 162, 135, 122, 37, 190, 248, 3, 132, 164, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}