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: 102e9f88dbc84e1b7e90b079f700ae0279a503658dcf887607930b4789bb5e98
Tx prefix hash: c028d07611d109470a998a2e111f3e5d193ec5bd9460abccc0e31c60b6d54d1c
Tx public key: 7a79a18dcfb38a7f7595f8dfcd0668d15f6b29efdaed847bd6e4a31a8c3be91e
| Timestamp: 1780687317 | Timestamp [UTC]: 2026-06-05 19:21:57 | Age [y:d:h:m:s]: 00:003:05:24:50 |
| Block: 5474 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2412 | RingCT/type: yes/0 |
| Extra: 017a79a18dcfb38a7f7595f8dfcd0668d15f6b29efdaed847bd6e4a31a8c3be91e020900000001e49593ff00 | ||
1 output(s) for total of 34.818995315061 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe6f085903ac4acfe74bab49219bd3745324c26db56d93410a063287f8d27a5e | 34.818995315061 | 6913 of 0 | <29> |
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": 5534,
"vin": [ {
"gen": {
"height": 5474
}
}
],
"vout": [ {
"amount": 34818995315061,
"target": {
"tagged_key": {
"key": "fe6f085903ac4acfe74bab49219bd3745324c26db56d93410a063287f8d27a5e",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 122, 121, 161, 141, 207, 179, 138, 127, 117, 149, 248, 223, 205, 6, 104, 209, 95, 107, 41, 239, 218, 237, 132, 123, 214, 228, 163, 26, 140, 59, 233, 30, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}