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: f1ec99b1cda2622d65348558219e9437c9db665fb01cca0adb88a5d08658095b
Tx prefix hash: 3b6465440eac444925cd331008a3dce0f5a14a905dd79cd18532defa772fef4b
Tx public key: 796528e45a15380a1c04ea8aeea46417cc499b027dc2daca753603916eacc962
| Timestamp: 1780323170 | Timestamp [UTC]: 2026-06-01 14:12:50 | Age [y:d:h:m:s]: 00:007:06:59:17 |
| Block: 5068 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2818 | RingCT/type: yes/0 |
| Extra: 01796528e45a15380a1c04ea8aeea46417cc499b027dc2daca753603916eacc96202090000005726697be300 | ||
1 output(s) for total of 34.845969040465 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1bea86670fe3d35ee49f7e72ea9d09244c7dddbb242f292ac46f76be6d9d57e4 | 34.845969040465 | 6443 of 0 | <df> |
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": 5128,
"vin": [ {
"gen": {
"height": 5068
}
}
],
"vout": [ {
"amount": 34845969040465,
"target": {
"tagged_key": {
"key": "1bea86670fe3d35ee49f7e72ea9d09244c7dddbb242f292ac46f76be6d9d57e4",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 121, 101, 40, 228, 90, 21, 56, 10, 28, 4, 234, 138, 238, 164, 100, 23, 204, 73, 155, 2, 125, 194, 218, 202, 117, 54, 3, 145, 110, 172, 201, 98, 2, 9, 0, 0, 0, 87, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}