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: 7e20ef37ed1418be6114851b2e5cfb86e4adcfda2cbb6b8f9ccc474636993bb5
Tx prefix hash: 8b2f02257b72f0aaafd7bacb7798a9701edbefeaf86f5d82eeeb6e87a8b631a8
Tx public key: 3ad32d82b9c7547bde511e94bac7051cd6fa0e94aa8b355a7e61755f7a2574e4
| Timestamp: 1779438053 | Timestamp [UTC]: 2026-05-22 08:20:53 | Age [y:d:h:m:s]: 00:017:21:17:46 |
| Block: 181 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7925 | RingCT/type: yes/0 |
| Extra: 013ad32d82b9c7547bde511e94bac7051cd6fa0e94aa8b355a7e61755f7a2574e40209000000015cddc08000 | ||
1 output(s) for total of 35.172294555272 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8effdfbaf681f97e09a48c7e540ba59ff16f729012a13ca920d7f369fd4b4c44 | 35.172294555272 | 177 of 0 | <10> |
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": 241,
"vin": [ {
"gen": {
"height": 181
}
}
],
"vout": [ {
"amount": 35172294555272,
"target": {
"tagged_key": {
"key": "8effdfbaf681f97e09a48c7e540ba59ff16f729012a13ca920d7f369fd4b4c44",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 58, 211, 45, 130, 185, 199, 84, 123, 222, 81, 30, 148, 186, 199, 5, 28, 214, 250, 14, 148, 170, 139, 53, 90, 126, 97, 117, 95, 122, 37, 116, 228, 2, 9, 0, 0, 0, 1, 92, 221, 192, 128, 0
],
"rct_signatures": {
"type": 0
}
}