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: 1ebc3ca399263bc01f0aed90325c2f2db69a8fe4138f96d46fdb0472d6f8c384
Tx prefix hash: e117cc1019914f1ca3249b1ac701e22e3ce55f2582992ea9b1d7168551c8e481
Tx public key: 943de07fff4ce70e096bd07c0f53405f295784e9415be9362857cc7084cf8b26
| Timestamp: 1779899262 | Timestamp [UTC]: 2026-05-27 16:27:42 | Age [y:d:h:m:s]: 00:012:06:51:11 |
| Block: 3125 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4761 | RingCT/type: yes/0 |
| Extra: 01943de07fff4ce70e096bd07c0f53405f295784e9415be9362857cc7084cf8b2602090000000126697be300 | ||
1 output(s) for total of 34.975347160398 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64db044a7a6c887c1216881ca643ca5c64b3ffbfd7c9fcfea5451b73e09ea8e5 | 34.975347160398 | 3733 of 0 | <f2> |
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": 3185,
"vin": [ {
"gen": {
"height": 3125
}
}
],
"vout": [ {
"amount": 34975347160398,
"target": {
"tagged_key": {
"key": "64db044a7a6c887c1216881ca643ca5c64b3ffbfd7c9fcfea5451b73e09ea8e5",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 148, 61, 224, 127, 255, 76, 231, 14, 9, 107, 208, 124, 15, 83, 64, 95, 41, 87, 132, 233, 65, 91, 233, 54, 40, 87, 204, 112, 132, 207, 139, 38, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}