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: cb1f342b56232b2016392b18513f136a2605e30a5775486140864c9ae182e57a
Tx prefix hash: 1506de404700670a2801f88daf7d98104487da0839f597caaf5a75620c9a5a7c
Tx public key: 0bd3bed454eda405d1a9994ba4f70071516a068d5acef451e231f952289c2d4c
| Timestamp: 1780397286 | Timestamp [UTC]: 2026-06-02 10:48:06 | Age [y:d:h:m:s]: 00:006:14:47:51 |
| Block: 5257 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2629 | RingCT/type: yes/0 |
| Extra: 010bd3bed454eda405d1a9994ba4f70071516a068d5acef451e231f952289c2d4c02090000000226697be300 | ||
1 output(s) for total of 34.833409707617 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6e7e53fdfef6ed709ef711424322f529e5a36ff4db5917bc9c35fcbfd2b7b00c | 34.833409707617 | 6658 of 0 | <a5> |
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": 5317,
"vin": [ {
"gen": {
"height": 5257
}
}
],
"vout": [ {
"amount": 34833409707617,
"target": {
"tagged_key": {
"key": "6e7e53fdfef6ed709ef711424322f529e5a36ff4db5917bc9c35fcbfd2b7b00c",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 11, 211, 190, 212, 84, 237, 164, 5, 209, 169, 153, 75, 164, 247, 0, 113, 81, 106, 6, 141, 90, 206, 244, 81, 226, 49, 249, 82, 40, 156, 45, 76, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}