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: 50039990f5e0693f6850d8f8bea38621b13a93873867da13dca18c76244a2322
Tx prefix hash: 349186923e3afab91b502060d076d35b368e52a888d44d69e0a93f4593a9c69f
Tx public key: 9720dde4857fab3ef7d6a469f19a182adc1fd45cbf769a928e76d28b9110f06a
| Timestamp: 1780123664 | Timestamp [UTC]: 2026-05-30 06:47:44 | Age [y:d:h:m:s]: 00:009:20:02:04 |
| Block: 4904 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2996 | RingCT/type: yes/0 |
| Extra: 019720dde4857fab3ef7d6a469f19a182adc1fd45cbf769a928e76d28b9110f06a02090000000126697be300 | ||
1 output(s) for total of 34.856870755300 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1915fb154e26526945899a3c890e81a09a2aa5eaa5d69be2e4cbee057361ed93 | 34.856870755300 | 6215 of 0 | <54> |
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": 4964,
"vin": [ {
"gen": {
"height": 4904
}
}
],
"vout": [ {
"amount": 34856870755300,
"target": {
"tagged_key": {
"key": "1915fb154e26526945899a3c890e81a09a2aa5eaa5d69be2e4cbee057361ed93",
"view_tag": "54"
}
}
}
],
"extra": [ 1, 151, 32, 221, 228, 133, 127, 171, 62, 247, 214, 164, 105, 241, 154, 24, 42, 220, 31, 212, 92, 191, 118, 154, 146, 142, 118, 210, 139, 145, 16, 240, 106, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}