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: 61e9a95f1520d9dbec9ec5af5b1a3baf7b859a4c7678c8c15d521ca29f0bfbbd
Tx prefix hash: 6de19b3b8b36408104dfc32b83e182f0b2b17795fd90172681b05a12f38d9f64
Tx public key: 186373d6a7f2af6f28c77f9bb22cc0ed717d5d93c6b569015f0490c30d8d17f9
| Timestamp: 1779439036 | Timestamp [UTC]: 2026-05-22 08:37:16 | Age [y:d:h:m:s]: 00:017:16:58:41 |
| Block: 199 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7687 | RingCT/type: yes/0 |
| Extra: 01186373d6a7f2af6f28c77f9bb22cc0ed717d5d93c6b569015f0490c30d8d17f9020900000005f2c813e500 | ||
1 output(s) for total of 35.171087029946 HMNY
| stealth address | amount | amount idx | tag |
| 00: f27cbb63f8923791b98c121619072ba1d7e3a0c391b5a4b94d638cf8ad3ae045 | 35.171087029946 | 195 of 0 | <eb> |
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": 259,
"vin": [ {
"gen": {
"height": 199
}
}
],
"vout": [ {
"amount": 35171087029946,
"target": {
"tagged_key": {
"key": "f27cbb63f8923791b98c121619072ba1d7e3a0c391b5a4b94d638cf8ad3ae045",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 24, 99, 115, 214, 167, 242, 175, 111, 40, 199, 127, 155, 178, 44, 192, 237, 113, 125, 93, 147, 198, 181, 105, 1, 95, 4, 144, 195, 13, 141, 23, 249, 2, 9, 0, 0, 0, 5, 242, 200, 19, 229, 0
],
"rct_signatures": {
"type": 0
}
}