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: 8805f7ee252395071c6a15abce9511a60b4956ca0dc5279f716c6a11e5a810c7
Tx prefix hash: 7b875b708c04ee8597f1b5589eba59f4cb06a85aaa37fc43a6887cd3b8672bd7
Tx public key: 8b4eafaff9d59afe7403813ff53c83efce7e0a8366f45c8557b1289cdb4bfc41
| Timestamp: 1779914764 | Timestamp [UTC]: 2026-05-27 20:46:04 | Age [y:d:h:m:s]: 00:012:04:49:53 |
| Block: 3286 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4600 | RingCT/type: yes/0 |
| Extra: 018b4eafaff9d59afe7403813ff53c83efce7e0a8366f45c8557b1289cdb4bfc4102090000000826697be300 | ||
1 output(s) for total of 34.964608460003 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1f4ebe2e800b43ce540311223a48b2a6895ee9cb79d096612ad4969490135bc | 34.964608460003 | 3946 of 0 | <94> |
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": 3346,
"vin": [ {
"gen": {
"height": 3286
}
}
],
"vout": [ {
"amount": 34964608460003,
"target": {
"tagged_key": {
"key": "c1f4ebe2e800b43ce540311223a48b2a6895ee9cb79d096612ad4969490135bc",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 139, 78, 175, 175, 249, 213, 154, 254, 116, 3, 129, 63, 245, 60, 131, 239, 206, 126, 10, 131, 102, 244, 92, 133, 87, 177, 40, 156, 219, 75, 252, 65, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}