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: ed5333da1b312b9778b32da193d104a6bd149dbfac093284b1de6e85a727f8c7
Tx prefix hash: b226b680390b4d35dfb87513ee0d316563040cc46ef377bd08f67ebdf5ab10fd
Tx public key: 32d3e200ca983a96b93293748b1025707922aec1a8f170d184a0abe6a984e623
| Timestamp: 1780829333 | Timestamp [UTC]: 2026-06-07 10:48:53 | Age [y:d:h:m:s]: 00:001:10:23:14 |
| Block: 7315 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 571 | RingCT/type: yes/0 |
| Extra: 0132d3e200ca983a96b93293748b1025707922aec1a8f170d184a0abe6a984e623020900000001e49593ff00 | ||
1 output(s) for total of 34.696945185160 HMNY
| stealth address | amount | amount idx | tag |
| 00: ef0dec2c27d4c5296610ac835e28f8aa3c54734905238a4b88dbfc513f553dcd | 34.696945185160 | 9005 of 0 | <e5> |
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": 7375,
"vin": [ {
"gen": {
"height": 7315
}
}
],
"vout": [ {
"amount": 34696945185160,
"target": {
"tagged_key": {
"key": "ef0dec2c27d4c5296610ac835e28f8aa3c54734905238a4b88dbfc513f553dcd",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 50, 211, 226, 0, 202, 152, 58, 150, 185, 50, 147, 116, 139, 16, 37, 112, 121, 34, 174, 193, 168, 241, 112, 209, 132, 160, 171, 230, 169, 132, 230, 35, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}