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: ce2768a0cd2250fa299a4264468ad9471877e9a8d28cc78823b8903ce46c9ef8
Tx prefix hash: df48a75301f68f8672c50a0274921438905325aeec0eedac12c692b06eb115c8
Tx public key: 5972f34701f57f482d90f6cc2faa9d62e05c1cd534fe72d8072bf75741fa0dea
| Timestamp: 1780062099 | Timestamp [UTC]: 2026-05-29 13:41:39 | Age [y:d:h:m:s]: 00:010:11:54:18 |
| Block: 4537 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3349 | RingCT/type: yes/0 |
| Extra: 015972f34701f57f482d90f6cc2faa9d62e05c1cd534fe72d8072bf75741fa0dea02090000000126697be300 | ||
1 output(s) for total of 34.881279023592 HMNY
| stealth address | amount | amount idx | tag |
| 00: 65ae56a5011d48b86e56f47fb5e2245fab07d1df944fae10baf8941666ebd708 | 34.881279023592 | 5692 of 0 | <3e> |
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": 4597,
"vin": [ {
"gen": {
"height": 4537
}
}
],
"vout": [ {
"amount": 34881279023592,
"target": {
"tagged_key": {
"key": "65ae56a5011d48b86e56f47fb5e2245fab07d1df944fae10baf8941666ebd708",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 89, 114, 243, 71, 1, 245, 127, 72, 45, 144, 246, 204, 47, 170, 157, 98, 224, 92, 28, 213, 52, 254, 114, 216, 7, 43, 247, 87, 65, 250, 13, 234, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}