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: 6b7232cc2c61c4d91576444703efafc28b234957003ed231c49fe9ea37f6def2
Tx prefix hash: a557342354897e94c75831cba3083f6247ac3ea9eec8094225160d1cc3d801d1
Tx public key: 5deae02a3df210b41f40285feffcafe8c65518b6178880714f8925766e4b14f7
| Timestamp: 1780079060 | Timestamp [UTC]: 2026-05-29 18:24:20 | Age [y:d:h:m:s]: 00:010:06:22:27 |
| Block: 4735 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3151 | RingCT/type: yes/0 |
| Extra: 015deae02a3df210b41f40285feffcafe8c65518b6178880714f8925766e4b14f702090000000726697be300 | ||
1 output(s) for total of 34.868108407711 HMNY
| stealth address | amount | amount idx | tag |
| 00: e382f633e9dd6173a97f05ea6f14b1a3c2da27631b36f3f94c08d4507c83c39a | 34.868108407711 | 5951 of 0 | <8a> |
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": 4795,
"vin": [ {
"gen": {
"height": 4735
}
}
],
"vout": [ {
"amount": 34868108407711,
"target": {
"tagged_key": {
"key": "e382f633e9dd6173a97f05ea6f14b1a3c2da27631b36f3f94c08d4507c83c39a",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 93, 234, 224, 42, 61, 242, 16, 180, 31, 64, 40, 95, 239, 252, 175, 232, 198, 85, 24, 182, 23, 136, 128, 113, 79, 137, 37, 118, 110, 75, 20, 247, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}