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: fb35d565c9e6a3df71b2752947ccb66166bbceb63935d2ee2f77f9ef7b299ce2
Tx prefix hash: f927f77dbb49d9a73d3b7760c93c2935d14317eee4c77b94cd60052ddb51a8fd
Tx public key: c479717abfe30c95cb29563de6962c8dca9d5f43e5737d547fa1d56eeb392d39
| Timestamp: 1779638252 | Timestamp [UTC]: 2026-05-24 15:57:32 | Age [y:d:h:m:s]: 00:015:11:41:18 |
| Block: 1187 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6757 | RingCT/type: yes/0 |
| Extra: 01c479717abfe30c95cb29563de6962c8dca9d5f43e5737d547fa1d56eeb392d39 | ||
1 output(s) for total of 35.104870854811 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9f4b027ad6f46304a77f60e5e74447948ebc4e62d138db757f3502d214b2fa91 | 35.104870854811 | 1331 of 0 | <1a> |
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": 1247,
"vin": [ {
"gen": {
"height": 1187
}
}
],
"vout": [ {
"amount": 35104870854811,
"target": {
"tagged_key": {
"key": "9f4b027ad6f46304a77f60e5e74447948ebc4e62d138db757f3502d214b2fa91",
"view_tag": "1a"
}
}
}
],
"extra": [ 1, 196, 121, 113, 122, 191, 227, 12, 149, 203, 41, 86, 61, 230, 150, 44, 141, 202, 157, 95, 67, 229, 115, 125, 84, 127, 161, 213, 110, 235, 57, 45, 57
],
"rct_signatures": {
"type": 0
}
}