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: e6896e3168f5d2670e6fbe306ebebea4108cb64b358f4e07a8db146f613a9da6
Tx prefix hash: fb76b817aa7b2e7c450d66b4d0d85ddd5d034fea71800c4be06e0ce7a3397bf1
Tx public key: 7853218d928fc3a46910c116d46c0dc71ae99762fde4b151d415c7cc47cebe84
| Timestamp: 1780804852 | Timestamp [UTC]: 2026-06-07 04:00:52 | Age [y:d:h:m:s]: 00:001:19:18:01 |
| Block: 6924 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 962 | RingCT/type: yes/0 |
| Extra: 017853218d928fc3a46910c116d46c0dc71ae99762fde4b151d415c7cc47cebe84020900000001e49593ff00 | ||
1 output(s) for total of 34.722830916937 HMNY
| stealth address | amount | amount idx | tag |
| 00: f0cb2cb8ffe75de6c197dcb54ba67a6ce16e0de5e44fd47558dfdea17b7c3f05 | 34.722830916937 | 8542 of 0 | <a6> |
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": 6984,
"vin": [ {
"gen": {
"height": 6924
}
}
],
"vout": [ {
"amount": 34722830916937,
"target": {
"tagged_key": {
"key": "f0cb2cb8ffe75de6c197dcb54ba67a6ce16e0de5e44fd47558dfdea17b7c3f05",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 120, 83, 33, 141, 146, 143, 195, 164, 105, 16, 193, 22, 212, 108, 13, 199, 26, 233, 151, 98, 253, 228, 177, 81, 212, 21, 199, 204, 71, 206, 190, 132, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}