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: b2bc1a234c6bd9c4951a50a09a0f689f33759c04c803eda5528a82881c34dc7f
Tx prefix hash: aa35afc021e80a91ffadb2b441b5caf744245e562c5e3258d1e601b6b99237b7
Tx public key: e6bb9fdeb7bfb0a3e5fcdce3793b12cb78a324e828fa81b9b09c5e5fc0910475
| Timestamp: 1779966793 | Timestamp [UTC]: 2026-05-28 11:13:13 | Age [y:d:h:m:s]: 00:011:14:22:44 |
| Block: 3815 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4071 | RingCT/type: yes/0 |
| Extra: 01e6bb9fdeb7bfb0a3e5fcdce3793b12cb78a324e828fa81b9b09c5e5fc091047502090000000226697be300 | ||
1 output(s) for total of 34.929347368049 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4f50dcdf46f9917b06df9267f4d5fc8e26b88417b278d10637fe34dcc397e562 | 34.929347368049 | 4644 of 0 | <22> |
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": 3875,
"vin": [ {
"gen": {
"height": 3815
}
}
],
"vout": [ {
"amount": 34929347368049,
"target": {
"tagged_key": {
"key": "4f50dcdf46f9917b06df9267f4d5fc8e26b88417b278d10637fe34dcc397e562",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 230, 187, 159, 222, 183, 191, 176, 163, 229, 252, 220, 227, 121, 59, 18, 203, 120, 163, 36, 232, 40, 250, 129, 185, 176, 156, 94, 95, 192, 145, 4, 117, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}