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: aea2b323754ec43134781117a2ab9d38127af393a8f88b57f0d2efd7761fb93a
Tx prefix hash: 0662d46c31f82a1365d8c1fdb13731e1910bf5e46d8cf3422a84e890fe479398
Tx public key: d5e71d1297bfe4cf5d9b570b86fc9dea4f8432ee7e0c735857ac80bf7f937d6b
| Timestamp: 1779456449 | Timestamp [UTC]: 2026-05-22 13:27:29 | Age [y:d:h:m:s]: 00:017:14:11:21 |
| Block: 390 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7558 | RingCT/type: yes/0 |
| Extra: 01d5e71d1297bfe4cf5d9b570b86fc9dea4f8432ee7e0c735857ac80bf7f937d6b02090000000293369e7d00 | ||
1 output(s) for total of 35.158276398121 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2cba8936152200750977db6831792c004995709956d624422a6c965ccbe75ef2 | 35.158276398121 | 390 of 0 | <ad> |
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": 450,
"vin": [ {
"gen": {
"height": 390
}
}
],
"vout": [ {
"amount": 35158276398121,
"target": {
"tagged_key": {
"key": "2cba8936152200750977db6831792c004995709956d624422a6c965ccbe75ef2",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 213, 231, 29, 18, 151, 191, 228, 207, 93, 155, 87, 11, 134, 252, 157, 234, 79, 132, 50, 238, 126, 12, 115, 88, 87, 172, 128, 191, 127, 147, 125, 107, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}