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: 983df1fb0f76914c59c0abd99cd68383138bfa573e94ed5c7f1999b135362ead
Tx prefix hash: bdc9586146f133a29a40782a416ee79e061ca44fb76b268e879f39e895f8167d
Tx public key: ee3f4c8761516627e25cac98c2ed20c4d34d0654d462cd5604bf07ec45831209
| Timestamp: 1779902351 | Timestamp [UTC]: 2026-05-27 17:19:11 | Age [y:d:h:m:s]: 00:012:08:16:46 |
| Block: 3158 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4728 | RingCT/type: yes/0 |
| Extra: 01ee3f4c8761516627e25cac98c2ed20c4d34d0654d462cd5604bf07ec4583120902090000000126697be300 | ||
1 output(s) for total of 34.980560591620 HMNY
| stealth address | amount | amount idx | tag |
| 00: d2585c24f9c0b2b451ec25a3802a63d0ee35a0ced843f53dc1feadf424db6b46 | 34.980560591620 | 3776 of 0 | <8d> |
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": 3218,
"vin": [ {
"gen": {
"height": 3158
}
}
],
"vout": [ {
"amount": 34980560591620,
"target": {
"tagged_key": {
"key": "d2585c24f9c0b2b451ec25a3802a63d0ee35a0ced843f53dc1feadf424db6b46",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 238, 63, 76, 135, 97, 81, 102, 39, 226, 92, 172, 152, 194, 237, 32, 196, 211, 77, 6, 84, 212, 98, 205, 86, 4, 191, 7, 236, 69, 131, 18, 9, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}