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: d3cc715d3d8cfb904895b88e2885f7c40bcf48f6280e0bae40a9dd3e44d9f843
Tx prefix hash: 2bee502bfa47a1a99b6cd08379c2ae87169e024b44f5e6d0e883ea9cf2716184
Tx public key: c112802ade14510b9e5537d832c8e0b68bc8570e9e1e7d9b8b542e43edf4aec2
| Timestamp: 1779693940 | Timestamp [UTC]: 2026-05-25 07:25:40 | Age [y:d:h:m:s]: 00:014:17:21:07 |
| Block: 1535 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6351 | RingCT/type: yes/0 |
| Extra: 01c112802ade14510b9e5537d832c8e0b68bc8570e9e1e7d9b8b542e43edf4aec2 | ||
1 output(s) for total of 35.081577448890 HMNY
| stealth address | amount | amount idx | tag |
| 00: 531bbbe29b360c4c06ddd386c70eddb9c631d72e78431b1e67a60b15d227b85e | 35.081577448890 | 1693 of 0 | <36> |
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": 1595,
"vin": [ {
"gen": {
"height": 1535
}
}
],
"vout": [ {
"amount": 35081577448890,
"target": {
"tagged_key": {
"key": "531bbbe29b360c4c06ddd386c70eddb9c631d72e78431b1e67a60b15d227b85e",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 193, 18, 128, 42, 222, 20, 81, 11, 158, 85, 55, 216, 50, 200, 224, 182, 139, 200, 87, 14, 158, 30, 125, 155, 139, 84, 46, 67, 237, 244, 174, 194
],
"rct_signatures": {
"type": 0
}
}