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: c1791ba4eeb8b466f84aa61c71919ba27861c1827f1811afe9a0cb070b241b03
Tx prefix hash: 043043b3690f6b9d37c6a1f6254e33561bb7026cdeba922e0dbeaa5d8804872b
Tx public key: c4f97edcb5a7798eb666787a5a8f75a4098a411ff1fad9586d60d7c31ad3dfb2
| Timestamp: 1779994210 | Timestamp [UTC]: 2026-05-28 18:50:10 | Age [y:d:h:m:s]: 00:011:09:00:48 |
| Block: 4013 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3954 | RingCT/type: yes/0 |
| Extra: 01c4f97edcb5a7798eb666787a5a8f75a4098a411ff1fad9586d60d7c31ad3dfb202090000000226697be300 | ||
1 output(s) for total of 34.918771002326 HMNY
| stealth address | amount | amount idx | tag |
| 00: b9e7d6db8f47e5956ff2928b7b91d5394e62fd6312eebee5e3da03209cad7a8a | 34.918771002326 | 4962 of 0 | <75> |
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": 4073,
"vin": [ {
"gen": {
"height": 4013
}
}
],
"vout": [ {
"amount": 34918771002326,
"target": {
"tagged_key": {
"key": "b9e7d6db8f47e5956ff2928b7b91d5394e62fd6312eebee5e3da03209cad7a8a",
"view_tag": "75"
}
}
}
],
"extra": [ 1, 196, 249, 126, 220, 181, 167, 121, 142, 182, 102, 120, 122, 90, 143, 117, 164, 9, 138, 65, 31, 241, 250, 217, 88, 109, 96, 215, 195, 26, 211, 223, 178, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}