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: 35e3627cede02c9bac8908004163214fc09204dd74cb96b5889e13c22affc98e
Tx prefix hash: 51a36f560a8046384d2c7631d6843aa8cf5b86a630d50fd3b8dbc9fd6ea8af1b
Tx public key: a7dfa9c4169da746650e1dde0636038af86395d17ca350c8fc0c402d59a4dc49
| Timestamp: 1780391961 | Timestamp [UTC]: 2026-06-02 09:19:21 | Age [y:d:h:m:s]: 00:006:13:59:32 |
| Block: 5215 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2671 | RingCT/type: yes/0 |
| Extra: 01a7dfa9c4169da746650e1dde0636038af86395d17ca350c8fc0c402d59a4dc4902090000000126697be300 | ||
1 output(s) for total of 34.838824679220 HMNY
| stealth address | amount | amount idx | tag |
| 00: 55f183535e8cb31724bc6a84faf87b5bd4a41f4c0e9f651a8f5d1c59d746408b | 34.838824679220 | 6598 of 0 | <34> |
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": 5275,
"vin": [ {
"gen": {
"height": 5215
}
}
],
"vout": [ {
"amount": 34838824679220,
"target": {
"tagged_key": {
"key": "55f183535e8cb31724bc6a84faf87b5bd4a41f4c0e9f651a8f5d1c59d746408b",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 167, 223, 169, 196, 22, 157, 167, 70, 101, 14, 29, 222, 6, 54, 3, 138, 248, 99, 149, 209, 124, 163, 80, 200, 252, 12, 64, 45, 89, 164, 220, 73, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}