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: 6f29a3a7147a109759993c0f40265ebbf5c3d9e161cc3a9277087176945682a8
Tx prefix hash: aaeb71250daa7e81b348ab04d9c9391f8fc20eb401270d83d7c63e5ea99a2854
Tx public key: 0dab6bb5ab962158d5288ce64a1d39689771cc1700c3689b3bcdc416d200557f
| Timestamp: 1779442952 | Timestamp [UTC]: 2026-05-22 09:42:32 | Age [y:d:h:m:s]: 00:017:15:53:25 |
| Block: 229 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7657 | RingCT/type: yes/0 |
| Extra: 010dab6bb5ab962158d5288ce64a1d39689771cc1700c3689b3bcdc416d200557f0209000000014438f87f00 | ||
1 output(s) for total of 35.169074579861 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf863df6b6263a81c6e90a87810e640954f4f4723a1ff8a96b979ef19beeb96f | 35.169074579861 | 225 of 0 | <6a> |
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": 289,
"vin": [ {
"gen": {
"height": 229
}
}
],
"vout": [ {
"amount": 35169074579861,
"target": {
"tagged_key": {
"key": "bf863df6b6263a81c6e90a87810e640954f4f4723a1ff8a96b979ef19beeb96f",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 13, 171, 107, 181, 171, 150, 33, 88, 213, 40, 140, 230, 74, 29, 57, 104, 151, 113, 204, 23, 0, 195, 104, 155, 59, 205, 196, 22, 210, 0, 85, 127, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}