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: 0062ecf8a48462ad9c0ea99d1db3589f89f22044da41423ae9b5d08381514a39
Tx prefix hash: 8fb73400608d50ca30a8431fbdea2c65b6b4050adcaee7eaed97e73d35814697
Tx public key: 35123ae004f139c62b8e1302a9a54039f965a497c9a3dec441a3967ee62d01f4
| Timestamp: 1780396835 | Timestamp [UTC]: 2026-06-02 10:40:35 | Age [y:d:h:m:s]: 00:006:14:55:22 |
| Block: 5256 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2630 | RingCT/type: yes/0 |
| Extra: 0135123ae004f139c62b8e1302a9a54039f965a497c9a3dec441a3967ee62d01f402090000000126697be300 | ||
1 output(s) for total of 34.833476147200 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7f1e7ca4b9a08b79017ba38444ee7d52ee480e49c3d14d6073c78e7ed78a187 | 34.833476147200 | 6657 of 0 | <f1> |
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": 5316,
"vin": [ {
"gen": {
"height": 5256
}
}
],
"vout": [ {
"amount": 34833476147200,
"target": {
"tagged_key": {
"key": "d7f1e7ca4b9a08b79017ba38444ee7d52ee480e49c3d14d6073c78e7ed78a187",
"view_tag": "f1"
}
}
}
],
"extra": [ 1, 53, 18, 58, 224, 4, 241, 57, 198, 43, 142, 19, 2, 169, 165, 64, 57, 249, 101, 164, 151, 201, 163, 222, 196, 65, 163, 150, 126, 230, 45, 1, 244, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}