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: 594fce5fc7772c72ddb0ba9f0262e27bc28e104b853d8553101472a131b3c60b
Tx prefix hash: 4b8b36a121894e04ae39780f1e78e0e553a8daaf1a7a4052c6fd00e870a0e458
Tx public key: 6ba376ccb2df8aa98c5c0ae00406f079d3a191f27a5c809d4c86abe8eac7c83f
| Timestamp: 1779882136 | Timestamp [UTC]: 2026-05-27 11:42:16 | Age [y:d:h:m:s]: 00:012:14:58:20 |
| Block: 2958 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4939 | RingCT/type: yes/0 |
| Extra: 016ba376ccb2df8aa98c5c0ae00406f079d3a191f27a5c809d4c86abe8eac7c83f02090000000226697be300 | ||
1 output(s) for total of 34.986489545665 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3542cc80fc59b5ce35649c013f2990d0f5aa9035c9fd6a1de8b6d45efbd34ad7 | 34.986489545665 | 3510 of 0 | <23> |
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": 3018,
"vin": [ {
"gen": {
"height": 2958
}
}
],
"vout": [ {
"amount": 34986489545665,
"target": {
"tagged_key": {
"key": "3542cc80fc59b5ce35649c013f2990d0f5aa9035c9fd6a1de8b6d45efbd34ad7",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 107, 163, 118, 204, 178, 223, 138, 169, 140, 92, 10, 224, 4, 6, 240, 121, 211, 161, 145, 242, 122, 92, 128, 157, 76, 134, 171, 232, 234, 199, 200, 63, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}