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: 7eb29c2b5b8164fb3c48d03012e913c21bbe0047a6d8e64acd6ab4ca43521cd9
Tx prefix hash: f69eb980baa1e456d6f8b865302635df9cc99fed9406a00e9438366496ed75ac
Tx public key: 83a06feb7a1261f31ee8337623c76961db8ddeb2da4393ce8726f389ab1c470f
| Timestamp: 1780828023 | Timestamp [UTC]: 2026-06-07 10:27:03 | Age [y:d:h:m:s]: 00:001:15:08:54 |
| Block: 7298 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 588 | RingCT/type: yes/0 |
| Extra: 0183a06feb7a1261f31ee8337623c76961db8ddeb2da4393ce8726f389ab1c470f020900000002e49593ff00 | ||
1 output(s) for total of 34.698070250380 HMNY
| stealth address | amount | amount idx | tag |
| 00: dcc5b4f98465cb574b2c13d354da0c281cc7eec30d7b7b7b2c50e71323961f65 | 34.698070250380 | 8984 of 0 | <1e> |
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": 7358,
"vin": [ {
"gen": {
"height": 7298
}
}
],
"vout": [ {
"amount": 34698070250380,
"target": {
"tagged_key": {
"key": "dcc5b4f98465cb574b2c13d354da0c281cc7eec30d7b7b7b2c50e71323961f65",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 131, 160, 111, 235, 122, 18, 97, 243, 30, 232, 51, 118, 35, 199, 105, 97, 219, 141, 222, 178, 218, 67, 147, 206, 135, 38, 243, 137, 171, 28, 71, 15, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}