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: 602ef06f08ce47b06b0fad81c66ed332f0acfb677d5faf1966a5145c275858ea
Tx prefix hash: edfeb799250061b2058bd542b8fe594fb15fe738dbac265a6411c83d2244dced
Tx public key: c8d1fd01e11fb543cac489d2898e2ea697edc6c1be2e0dcf9d6a8f570fc272b4
| Timestamp: 1779638364 | Timestamp [UTC]: 2026-05-24 15:59:24 | Age [y:d:h:m:s]: 00:015:10:50:24 |
| Block: 1194 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6726 | RingCT/type: yes/0 |
| Extra: 01c8d1fd01e11fb543cac489d2898e2ea697edc6c1be2e0dcf9d6a8f570fc272b4020900000001ba6d17be00 | ||
1 output(s) for total of 35.104402156901 HMNY
| stealth address | amount | amount idx | tag |
| 00: 46a41b26cb3436a9b22a4ad932e51858e960fde8293cba7b09d516b781260391 | 35.104402156901 | 1338 of 0 | <2d> |
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": 1254,
"vin": [ {
"gen": {
"height": 1194
}
}
],
"vout": [ {
"amount": 35104402156901,
"target": {
"tagged_key": {
"key": "46a41b26cb3436a9b22a4ad932e51858e960fde8293cba7b09d516b781260391",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 200, 209, 253, 1, 225, 31, 181, 67, 202, 196, 137, 210, 137, 142, 46, 166, 151, 237, 198, 193, 190, 46, 13, 207, 157, 106, 143, 87, 15, 194, 114, 180, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}