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: 262116b1cf1a1286a293c3b55a58b7d42e7d4d28b0b0c0b70afee566a75eea6e
Tx prefix hash: ca8c79d82d61cbc6236e622693e4bc97e79060b2bdbbe0bd3d40a328a5e82bb5
Tx public key: a5b9422602e040b6cdb93e84b9db4328ceb57ec260623bee3268f802989b88a7
| Timestamp: 1779479914 | Timestamp [UTC]: 2026-05-22 19:58:34 | Age [y:d:h:m:s]: 00:017:05:37:23 |
| Block: 640 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7246 | RingCT/type: yes/0 |
| Extra: 01a5b9422602e040b6cdb93e84b9db4328ceb57ec260623bee3268f802989b88a702090000000293369e7d00 | ||
1 output(s) for total of 35.141515605933 HMNY
| stealth address | amount | amount idx | tag |
| 00: b9b4ef2c123e08a0d0ecf02b20fe8ad834500734ae18aeed51b0d648a4982bca | 35.141515605933 | 680 of 0 | <e7> |
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": 700,
"vin": [ {
"gen": {
"height": 640
}
}
],
"vout": [ {
"amount": 35141515605933,
"target": {
"tagged_key": {
"key": "b9b4ef2c123e08a0d0ecf02b20fe8ad834500734ae18aeed51b0d648a4982bca",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 165, 185, 66, 38, 2, 224, 64, 182, 205, 185, 62, 132, 185, 219, 67, 40, 206, 181, 126, 194, 96, 98, 59, 238, 50, 104, 248, 2, 152, 155, 136, 167, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}