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: 4d7e84f9d81d44d0378169b92ea461926ebf298d7390a68eba3b3a47acb7c80a
Tx prefix hash: 8d0155de2f8d15464d20aefd289f4e7ef73acc6f96cb9553b676446811126220
Tx public key: 01d33691c78633eab7fe88e9f1a0a531b408d985bf9842256fa15e4840369a74
| Timestamp: 1779639933 | Timestamp [UTC]: 2026-05-24 16:25:33 | Age [y:d:h:m:s]: 00:015:06:53:20 |
| Block: 1267 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6619 | RingCT/type: yes/0 |
| Extra: 0101d33691c78633eab7fe88e9f1a0a531b408d985bf9842256fa15e4840369a74020900000001ba6d17be00 | ||
1 output(s) for total of 35.099514680162 HMNY
| stealth address | amount | amount idx | tag |
| 00: be6ef6c0b17d4281454a21709541e4507077b07631eb489971d7fe43351b67b5 | 35.099514680162 | 1413 of 0 | <50> |
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": 1327,
"vin": [ {
"gen": {
"height": 1267
}
}
],
"vout": [ {
"amount": 35099514680162,
"target": {
"tagged_key": {
"key": "be6ef6c0b17d4281454a21709541e4507077b07631eb489971d7fe43351b67b5",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 1, 211, 54, 145, 199, 134, 51, 234, 183, 254, 136, 233, 241, 160, 165, 49, 180, 8, 217, 133, 191, 152, 66, 37, 111, 161, 94, 72, 64, 54, 154, 116, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}