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: d331b5fca330bd23454163ba635ae3cbae7020a711c9ff707e02fe82d7b437c3
Tx prefix hash: 73c80ff9ac5547697cce6b0b1b45b3d5e51a9f9d16f4e5eb6c5b5afec6b763d6
Tx public key: 8533109a0a52b0409927f2845f6cb50487d42dd23d26de6361a6a11da491ea2f
| Timestamp: 1779476601 | Timestamp [UTC]: 2026-05-22 19:03:21 | Age [y:d:h:m:s]: 00:021:15:58:55 |
| Block: 617 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8128 | RingCT/type: yes/0 |
| Extra: 018533109a0a52b0409927f2845f6cb50487d42dd23d26de6361a6a11da491ea2f02090000000293369e7d00 | ||
1 output(s) for total of 35.148738065019 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3fa4a3f1df1155b4587308e84144dd364f9ca34df4e36136bd4cde0e5d5072a7 | 35.148738065019 | 639 of 0 | <39> |
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": 677,
"vin": [ {
"gen": {
"height": 617
}
}
],
"vout": [ {
"amount": 35148738065019,
"target": {
"tagged_key": {
"key": "3fa4a3f1df1155b4587308e84144dd364f9ca34df4e36136bd4cde0e5d5072a7",
"view_tag": "39"
}
}
}
],
"extra": [ 1, 133, 51, 16, 154, 10, 82, 176, 64, 153, 39, 242, 132, 95, 108, 181, 4, 135, 212, 45, 210, 61, 38, 222, 99, 97, 166, 161, 29, 164, 145, 234, 47, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}