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: a9fa723b361590780a04b81787fec1ea0582ccbbcd597ac71c8b297e74cbab47
Tx prefix hash: 5b27e0fb18a4a6a22fdab34bcb7e9c33e385c506c16bde390474d72673a7fce9
Tx public key: ba0fd355330e3e34e7a4ead966cf7572ebc95ac4517e6dc2ea44027ac94758c1
| Timestamp: 1780993252 | Timestamp [UTC]: 2026-06-09 08:20:52 | Age [y:d:h:m:s]: 00:000:08:59:11 |
| Block: 8275 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 468 | RingCT/type: yes/0 |
| Extra: 01ba0fd355330e3e34e7a4ead966cf7572ebc95ac4517e6dc2ea44027ac94758c1020900000001e49593ff00 | ||
1 output(s) for total of 34.633471250361 HMNY
| stealth address | amount | amount idx | tag |
| 00: 361bc2d15750456310f6b3f898a28efe545b8ee7ffa3e103ea053b13b450c76e | 34.633471250361 | 10241 of 0 | <cf> |
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": 8335,
"vin": [ {
"gen": {
"height": 8275
}
}
],
"vout": [ {
"amount": 34633471250361,
"target": {
"tagged_key": {
"key": "361bc2d15750456310f6b3f898a28efe545b8ee7ffa3e103ea053b13b450c76e",
"view_tag": "cf"
}
}
}
],
"extra": [ 1, 186, 15, 211, 85, 51, 14, 62, 52, 231, 164, 234, 217, 102, 207, 117, 114, 235, 201, 90, 196, 81, 126, 109, 194, 234, 68, 2, 122, 201, 71, 88, 193, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}