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: d875ad3092b645805e2ed9666d9094abb61ef81a4ec41416acafa8bb58ebce99
Tx prefix hash: d9e3ff3b5b9b5b81e787aac2b7fb887e4fef7f33fb6b6242acef612db3bb6ead
Tx public key: 39b9adc1fd92e0d64d094f16dc27ccdf66b0de3eeed8cb295621863a6f35eeea
| Timestamp: 1779846237 | Timestamp [UTC]: 2026-05-27 01:43:57 | Age [y:d:h:m:s]: 00:013:01:05:51 |
| Block: 2455 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5465 | RingCT/type: yes/0 |
| Extra: 0139b9adc1fd92e0d64d094f16dc27ccdf66b0de3eeed8cb295621863a6f35eeea02090000000126697be300 | ||
1 output(s) for total of 35.020071595163 HMNY
| stealth address | amount | amount idx | tag |
| 00: 72e7d2a1279a99e9bdc11c7a056173b9c2cce4f1f6909dad85ffe7438fc1c836 | 35.020071595163 | 2887 of 0 | <44> |
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": 2515,
"vin": [ {
"gen": {
"height": 2455
}
}
],
"vout": [ {
"amount": 35020071595163,
"target": {
"tagged_key": {
"key": "72e7d2a1279a99e9bdc11c7a056173b9c2cce4f1f6909dad85ffe7438fc1c836",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 57, 185, 173, 193, 253, 146, 224, 214, 77, 9, 79, 22, 220, 39, 204, 223, 102, 176, 222, 62, 238, 216, 203, 41, 86, 33, 134, 58, 111, 53, 238, 234, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}