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: 2987705ada98c760a4c1cffdc39d670467e2783c3ef983ab5859d738ece34c53
Tx prefix hash: 30368a3a303433b0ea091a6f67c92904f1ae647c83f1815f7739a8b4a2cdc0fa
Tx public key: d8c86527f787920364f9383f7a8466bd27438967b5832e85d47c3b328444057d
| Timestamp: 1779641857 | Timestamp [UTC]: 2026-05-24 16:57:37 | Age [y:d:h:m:s]: 00:015:08:38:20 |
| Block: 1363 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6523 | RingCT/type: yes/0 |
| Extra: 01d8c86527f787920364f9383f7a8466bd27438967b5832e85d47c3b328444057d020900000001ba6d17be00 | ||
1 output(s) for total of 35.093088349311 HMNY
| stealth address | amount | amount idx | tag |
| 00: 35bb965b335658caf82017f3ee31d159bb94c91a218bea3e6af96d347346b4ca | 35.093088349311 | 1513 of 0 | <90> |
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": 1423,
"vin": [ {
"gen": {
"height": 1363
}
}
],
"vout": [ {
"amount": 35093088349311,
"target": {
"tagged_key": {
"key": "35bb965b335658caf82017f3ee31d159bb94c91a218bea3e6af96d347346b4ca",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 216, 200, 101, 39, 247, 135, 146, 3, 100, 249, 56, 63, 122, 132, 102, 189, 39, 67, 137, 103, 181, 131, 46, 133, 212, 124, 59, 50, 132, 68, 5, 125, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}