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: bdbf4daa942053145303647e4aa1cd31dc33e03f6e26b21bbf4fb0fa49d2c626
Tx prefix hash: 687794e1fb3ae8e869f675ed0028f6d636cac44ed680f5ee06f922ebaa5ef704
Tx public key: 46dcb291a9220e092a887dbd1a75b32db8fa7a8c51650661cb5ace816b52ace7
| Timestamp: 1779641061 | Timestamp [UTC]: 2026-05-24 16:44:21 | Age [y:d:h:m:s]: 00:015:10:54:29 |
| Block: 1317 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6628 | RingCT/type: yes/0 |
| Extra: 0146dcb291a9220e092a887dbd1a75b32db8fa7a8c51650661cb5ace816b52ace7020900000001ba6d17be00 | ||
1 output(s) for total of 35.096167486012 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7a63b82453875ea63dfb68a4f740060c2cf9dc7bc66e9fb180bfb5eb1eff5366 | 35.096167486012 | 1465 of 0 | <d4> |
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": 1377,
"vin": [ {
"gen": {
"height": 1317
}
}
],
"vout": [ {
"amount": 35096167486012,
"target": {
"tagged_key": {
"key": "7a63b82453875ea63dfb68a4f740060c2cf9dc7bc66e9fb180bfb5eb1eff5366",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 70, 220, 178, 145, 169, 34, 14, 9, 42, 136, 125, 189, 26, 117, 179, 45, 184, 250, 122, 140, 81, 101, 6, 97, 203, 90, 206, 129, 107, 82, 172, 231, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}