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: dc35efcacfdda1414ea71670d0726dfb8d589af96b69394644771790ecb806ca
Tx prefix hash: c2f098690a317770f9c7c497428657ff681a5e48e427e81627f428282e376ff7
Tx public key: 3e280202e17963914c7b293ba92fa4f1a2976816898d0fb96456612e04db4376
| Timestamp: 1779474663 | Timestamp [UTC]: 2026-05-22 18:31:03 | Age [y:d:h:m:s]: 00:017:06:15:44 |
| Block: 600 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7286 | RingCT/type: yes/0 |
| Extra: 013e280202e17963914c7b293ba92fa4f1a2976816898d0fb96456612e04db437602090000000293369e7d00 | ||
1 output(s) for total of 35.149173195638 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1219f1d72f87ea19a4eb267522a8be040bff4b11b379011c96ea52c07c2c2d1 | 35.149173195638 | 614 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": 660,
"vin": [ {
"gen": {
"height": 600
}
}
],
"vout": [ {
"amount": 35149173195638,
"target": {
"tagged_key": {
"key": "c1219f1d72f87ea19a4eb267522a8be040bff4b11b379011c96ea52c07c2c2d1",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 62, 40, 2, 2, 225, 121, 99, 145, 76, 123, 41, 59, 169, 47, 164, 241, 162, 151, 104, 22, 137, 141, 15, 185, 100, 86, 97, 46, 4, 219, 67, 118, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}