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: e205c9d3861350d85d2661d15e7de869ad528f7b265ba5387faa82be63d4f6d5
Tx prefix hash: 306623be8d00212e16b143794db1318791df41bf9cfec4fe1373d9669ac7426e
Tx public key: 416353fe1fcca0c5e535c3d75d9ae15396ab05c99caeced9fe716677fb784f49
| Timestamp: 1780012658 | Timestamp [UTC]: 2026-05-28 23:57:38 | Age [y:d:h:m:s]: 00:011:02:52:10 |
| Block: 4106 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3814 | RingCT/type: yes/0 |
| Extra: 01416353fe1fcca0c5e535c3d75d9ae15396ab05c99caeced9fe716677fb784f4902090000000626697be300 | ||
1 output(s) for total of 34.909965597979 HMNY
| stealth address | amount | amount idx | tag |
| 00: a2009edd6931b7db3332b5d6b5584c97b6cc0104328a9883a99c69830e12c0cc | 34.909965597979 | 5113 of 0 | <52> |
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": 4166,
"vin": [ {
"gen": {
"height": 4106
}
}
],
"vout": [ {
"amount": 34909965597979,
"target": {
"tagged_key": {
"key": "a2009edd6931b7db3332b5d6b5584c97b6cc0104328a9883a99c69830e12c0cc",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 65, 99, 83, 254, 31, 204, 160, 197, 229, 53, 195, 215, 93, 154, 225, 83, 150, 171, 5, 201, 156, 174, 206, 217, 254, 113, 102, 119, 251, 120, 79, 73, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}