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: 698bd38c1e24a3f93ca32734537e4c936a66c259c676d32212610a33a30f08ff
Tx prefix hash: aa72f1307bba89e481543ae09d30c0f64edc6546147edc561a0f7065e1bea208
Tx public key: 408e85f3d87476ee477b57c5599c75acbce07d05b789c5130f51e9f41af0daf9
| Timestamp: 1779784790 | Timestamp [UTC]: 2026-05-26 08:39:50 | Age [y:d:h:m:s]: 00:013:16:56:07 |
| Block: 2151 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5735 | RingCT/type: yes/0 |
| Extra: 01408e85f3d87476ee477b57c5599c75acbce07d05b789c5130f51e9f41af0daf902090000000226697be300 | ||
1 output(s) for total of 35.049373730328 HMNY
| stealth address | amount | amount idx | tag |
| 00: b0fad8e093a46c895a051f912ac88f92321430beb0337da278fe370657febd49 | 35.049373730328 | 2481 of 0 | <f9> |
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": 2211,
"vin": [ {
"gen": {
"height": 2151
}
}
],
"vout": [ {
"amount": 35049373730328,
"target": {
"tagged_key": {
"key": "b0fad8e093a46c895a051f912ac88f92321430beb0337da278fe370657febd49",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 64, 142, 133, 243, 216, 116, 118, 238, 71, 123, 87, 197, 89, 156, 117, 172, 188, 224, 125, 5, 183, 137, 197, 19, 15, 81, 233, 244, 26, 240, 218, 249, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}