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: 421651280400d8b8fb440fc1ec3027a73f61194b5fd87549e07db262855d30ca
Tx prefix hash: f0a8cb02db5d3e2e4826d643d8f14653d2352c46da307066a8a2ae39d1e67830
Tx public key: a413014f019f91632bbc2fd59624940cb9ee3f14b44b41b3e06b52ab6b8dbd8b
| Timestamp: 1780065899 | Timestamp [UTC]: 2026-05-29 14:44:59 | Age [y:d:h:m:s]: 00:010:10:50:58 |
| Block: 4585 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3301 | RingCT/type: yes/0 |
| Extra: 01a413014f019f91632bbc2fd59624940cb9ee3f14b44b41b3e06b52ab6b8dbd8b02090000000126697be300 | ||
1 output(s) for total of 34.878085690255 HMNY
| stealth address | amount | amount idx | tag |
| 00: fffea53b9f7778e4a891fdf19b8b813b0e54c57b129dfb4df0d361bcc311d6e4 | 34.878085690255 | 5755 of 0 | <ed> |
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": 4645,
"vin": [ {
"gen": {
"height": 4585
}
}
],
"vout": [ {
"amount": 34878085690255,
"target": {
"tagged_key": {
"key": "fffea53b9f7778e4a891fdf19b8b813b0e54c57b129dfb4df0d361bcc311d6e4",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 164, 19, 1, 79, 1, 159, 145, 99, 43, 188, 47, 213, 150, 36, 148, 12, 185, 238, 63, 20, 180, 75, 65, 179, 224, 107, 82, 171, 107, 141, 189, 139, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}