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: d377e6174e992238c7a5e4e4b9abc80d2b205ac35ecedeca4ac71f9e7d36d944
Tx prefix hash: 92c1f8d70f4741581f391fd6c2bdf3405ae7d59262f0721d845b87659b1674af
Tx public key: 16a64a836ae5df4896575cadb512f50eb17563754461d2915a767bd6d2d78492
| Timestamp: 1779916660 | Timestamp [UTC]: 2026-05-27 21:17:40 | Age [y:d:h:m:s]: 00:012:06:33:18 |
| Block: 3316 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4646 | RingCT/type: yes/0 |
| Extra: 0116a64a836ae5df4896575cadb512f50eb17563754461d2915a767bd6d2d7849202090000000126697be300 | ||
1 output(s) for total of 34.962607824390 HMNY
| stealth address | amount | amount idx | tag |
| 00: 24b59aa03bceff3edb89d0af72f3acb002d6f6ad22f6fd5293d934076fba13fb | 34.962607824390 | 3982 of 0 | <b8> |
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": 3376,
"vin": [ {
"gen": {
"height": 3316
}
}
],
"vout": [ {
"amount": 34962607824390,
"target": {
"tagged_key": {
"key": "24b59aa03bceff3edb89d0af72f3acb002d6f6ad22f6fd5293d934076fba13fb",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 22, 166, 74, 131, 106, 229, 223, 72, 150, 87, 92, 173, 181, 18, 245, 14, 177, 117, 99, 117, 68, 97, 210, 145, 90, 118, 123, 214, 210, 215, 132, 146, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}