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: c39d113bca487e4df5cb7c7b5a90669d5ea946c787ac3e22903efaa90a70bd55
Tx prefix hash: 99babb78937867c6f155d70557c89052060545e2bc8ec20be38e3268f903e473
Tx public key: 83accd3648d34bd1929b9124c4f1014d85235e86ab659def1e5de9fda655e37a
| Timestamp: 1779780450 | Timestamp [UTC]: 2026-05-26 07:27:30 | Age [y:d:h:m:s]: 00:013:20:11:20 |
| Block: 2098 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5846 | RingCT/type: yes/0 |
| Extra: 0183accd3648d34bd1929b9124c4f1014d85235e86ab659def1e5de9fda655e37a02090000000126697be300 | ||
1 output(s) for total of 35.043925726797 HMNY
| stealth address | amount | amount idx | tag |
| 00: ceba4ecb6d851beed4e636937bbb90e181ad88d03f18cb05f00f1099bf4fd9d4 | 35.043925726797 | 2414 of 0 | <14> |
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": 2158,
"vin": [ {
"gen": {
"height": 2098
}
}
],
"vout": [ {
"amount": 35043925726797,
"target": {
"tagged_key": {
"key": "ceba4ecb6d851beed4e636937bbb90e181ad88d03f18cb05f00f1099bf4fd9d4",
"view_tag": "14"
}
}
}
],
"extra": [ 1, 131, 172, 205, 54, 72, 211, 75, 209, 146, 155, 145, 36, 196, 241, 1, 77, 133, 35, 94, 134, 171, 101, 157, 239, 30, 93, 233, 253, 166, 85, 227, 122, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}