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: 9d3468c9ccd0577c87a092e874f1a0c32743974f318b1e3370db13ceb4155572
Tx prefix hash: 388707b7293dbc4a4289cc307fc68e1ce753c461b6d4e3c688449b7ba5fadde9
Tx public key: 95be0b62cef1ad90faaff17762e10dd88bf9de59c95b97352a7fc2a657eebc93
| Timestamp: 1779633060 | Timestamp [UTC]: 2026-05-24 14:31:00 | Age [y:d:h:m:s]: 00:015:12:18:48 |
| Block: 973 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6926 | RingCT/type: yes/0 |
| Extra: 0195be0b62cef1ad90faaff17762e10dd88bf9de59c95b97352a7fc2a657eebc93020900000001ba6d17be00 | ||
1 output(s) for total of 35.119202639871 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9c735aabd4986d2639a0faa7ec6a88b1b634de089eb7e6a6fc7e9e813f402f84 | 35.119202639871 | 1109 of 0 | <d1> |
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": 1033,
"vin": [ {
"gen": {
"height": 973
}
}
],
"vout": [ {
"amount": 35119202639871,
"target": {
"tagged_key": {
"key": "9c735aabd4986d2639a0faa7ec6a88b1b634de089eb7e6a6fc7e9e813f402f84",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 149, 190, 11, 98, 206, 241, 173, 144, 250, 175, 241, 119, 98, 225, 13, 216, 139, 249, 222, 89, 201, 91, 151, 53, 42, 127, 194, 166, 87, 238, 188, 147, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}