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: 6e9eedadc0742a36a9116da8418ae363c2bbb2e6d7ceca8e9269831850ac6dc1
Tx prefix hash: b1ef37d241ccf2afdef74fdaedff3c2d3ab898954bb21e5a18915e02937172d1
Tx public key: 26fdf99895386c078af10f47ab5280fef3997b75ddd0e9910e0767d82c68d079
| Timestamp: 1779845925 | Timestamp [UTC]: 2026-05-27 01:38:45 | Age [y:d:h:m:s]: 00:012:23:57:12 |
| Block: 2449 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5437 | RingCT/type: yes/0 |
| Extra: 0126fdf99895386c078af10f47ab5280fef3997b75ddd0e9910e0767d82c68d07902090000000126697be300 | ||
1 output(s) for total of 35.027867970753 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c848e34560f971f1ea69abd65ece3adbe90b5f9312e4a58baf1e27c3844e6da | 35.027867970753 | 2879 of 0 | <38> |
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": 2509,
"vin": [ {
"gen": {
"height": 2449
}
}
],
"vout": [ {
"amount": 35027867970753,
"target": {
"tagged_key": {
"key": "8c848e34560f971f1ea69abd65ece3adbe90b5f9312e4a58baf1e27c3844e6da",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 38, 253, 249, 152, 149, 56, 108, 7, 138, 241, 15, 71, 171, 82, 128, 254, 243, 153, 123, 117, 221, 208, 233, 145, 14, 7, 103, 216, 44, 104, 208, 121, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}