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: ba51c40f57105774b788c4659e8d8c356a6f1d5b177ff9cd04f0219655eee6b0
Tx prefix hash: cce1089317e168991ad9d6485ce114802fd354e3d6a9c31fbc6e257cd950da9a
Tx public key: 70267023e4d11b1881e495fd5aed751b0252d71d1ac0fb0dec4982c93f700833
| Timestamp: 1779630739 | Timestamp [UTC]: 2026-05-24 13:52:19 | Age [y:d:h:m:s]: 00:015:12:57:29 |
| Block: 884 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7036 | RingCT/type: yes/0 |
| Extra: 0170267023e4d11b1881e495fd5aed751b0252d71d1ac0fb0dec4982c93f700833020900000001ba6d17be00 | ||
1 output(s) for total of 35.125164777710 HMNY
| stealth address | amount | amount idx | tag |
| 00: dc8cf869430744939cfd47d700deb37afb747e9848aedc1fdedbdbf7abe03039 | 35.125164777710 | 1016 of 0 | <0e> |
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": 944,
"vin": [ {
"gen": {
"height": 884
}
}
],
"vout": [ {
"amount": 35125164777710,
"target": {
"tagged_key": {
"key": "dc8cf869430744939cfd47d700deb37afb747e9848aedc1fdedbdbf7abe03039",
"view_tag": "0e"
}
}
}
],
"extra": [ 1, 112, 38, 112, 35, 228, 209, 27, 24, 129, 228, 149, 253, 90, 237, 117, 27, 2, 82, 215, 29, 26, 192, 251, 13, 236, 73, 130, 201, 63, 112, 8, 51, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}