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: 3302f508f0b06042ddea96cd80166a40932051d7f9bd679cf62f279784716d77
Tx prefix hash: a8c8f9d7273c042d2ee77e6f2bdf7f1a3a30d8240b7fc35b2c40a18d24795ee5
Tx public key: fee027083c40e426171f64a188bfa4fa8c057156581a2f6f98443e53bbc54972
| Timestamp: 1779457342 | Timestamp [UTC]: 2026-05-22 13:42:22 | Age [y:d:h:m:s]: 00:017:11:53:35 |
| Block: 399 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7487 | RingCT/type: yes/0 |
| Extra: 01fee027083c40e426171f64a188bfa4fa8c057156581a2f6f98443e53bbc5497202090000000193369e7d00 | ||
1 output(s) for total of 35.157672870912 HMNY
| stealth address | amount | amount idx | tag |
| 00: de9ff332f54057ab04a4afaf616a257050e0e098ef7e5e97e1403afe41e829e1 | 35.157672870912 | 399 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": 459,
"vin": [ {
"gen": {
"height": 399
}
}
],
"vout": [ {
"amount": 35157672870912,
"target": {
"tagged_key": {
"key": "de9ff332f54057ab04a4afaf616a257050e0e098ef7e5e97e1403afe41e829e1",
"view_tag": "75"
}
}
}
],
"extra": [ 1, 254, 224, 39, 8, 60, 64, 228, 38, 23, 31, 100, 161, 136, 191, 164, 250, 140, 5, 113, 86, 88, 26, 47, 111, 152, 68, 62, 83, 187, 197, 73, 114, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}