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: 2477012777916fc1dfc991767a04d6b2a9db53b4a1a242317454118d341c8b73
Tx prefix hash: ce1d2d7b53f2d51e6cabe4a8cb5ef7c89bdd2838aebeba639c460f243053b693
Tx public key: d4963898ecccabfd13b94bf5b8ea31df3d2da691207138ae56264c8c1b867e72
| Timestamp: 1779840307 | Timestamp [UTC]: 2026-05-27 00:05:07 | Age [y:d:h:m:s]: 00:013:01:30:50 |
| Block: 2383 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5503 | RingCT/type: yes/0 |
| Extra: 01d4963898ecccabfd13b94bf5b8ea31df3d2da691207138ae56264c8c1b867e7202090000000126697be300 | ||
1 output(s) for total of 35.024881204961 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a24d3e923ab9aa82a4b82ac72a9f898f46a81324be0ca5bc255c2b83c7bb1a5 | 35.024881204961 | 2795 of 0 | <69> |
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": 2443,
"vin": [ {
"gen": {
"height": 2383
}
}
],
"vout": [ {
"amount": 35024881204961,
"target": {
"tagged_key": {
"key": "0a24d3e923ab9aa82a4b82ac72a9f898f46a81324be0ca5bc255c2b83c7bb1a5",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 212, 150, 56, 152, 236, 204, 171, 253, 19, 185, 75, 245, 184, 234, 49, 223, 61, 45, 166, 145, 32, 113, 56, 174, 86, 38, 76, 140, 27, 134, 126, 114, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}