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: 7501a16794bbe2657d1fc2b8aa2b62f3e6d18d84c7d81b432e2732d60aa8f995
Tx prefix hash: 010f1bbd71bd1f9ba8bbfcf7341b37769d1b691dc0be2cb3c0b7fd7cf3b73407
Tx public key: ea7f13ea551b9e2df483da4323efe120f9535f2100e08c9aec16a28623402bd3
| Timestamp: 1779800322 | Timestamp [UTC]: 2026-05-26 12:58:42 | Age [y:d:h:m:s]: 00:013:12:37:15 |
| Block: 2299 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5587 | RingCT/type: yes/0 |
| Extra: 01ea7f13ea551b9e2df483da4323efe120f9535f2100e08c9aec16a28623402bd302090000000326697be300 | ||
1 output(s) for total of 35.035494851254 HMNY
| stealth address | amount | amount idx | tag |
| 00: 740d3ebc25a1d3dfd33cddd14edd700d055dce471bbce4a73dfcce65e9303991 | 35.035494851254 | 2681 of 0 | <2d> |
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": 2359,
"vin": [ {
"gen": {
"height": 2299
}
}
],
"vout": [ {
"amount": 35035494851254,
"target": {
"tagged_key": {
"key": "740d3ebc25a1d3dfd33cddd14edd700d055dce471bbce4a73dfcce65e9303991",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 234, 127, 19, 234, 85, 27, 158, 45, 244, 131, 218, 67, 35, 239, 225, 32, 249, 83, 95, 33, 0, 224, 140, 154, 236, 22, 162, 134, 35, 64, 43, 211, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}