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: 41562e9373fbb845c7a3ee19995b2552b689927c9bf51298fccba76dc56dcd75
Tx prefix hash: 72a68a8c8b80438d3e46358569ecbfa72f44b7119b9faa43bb01e3b296a65cc9
Tx public key: 004a3c54791e77d07e31e6bdc3c1fbd48ed4aa0bb4bc80685b8bd20e2ae43fc1
| Timestamp: 1780084033 | Timestamp [UTC]: 2026-05-29 19:47:13 | Age [y:d:h:m:s]: 00:018:12:41:59 |
| Block: 4795 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3950 | RingCT/type: yes/0 |
| Extra: 01004a3c54791e77d07e31e6bdc3c1fbd48ed4aa0bb4bc80685b8bd20e2ae43fc102090000000126697be300 | ||
1 output(s) for total of 34.864118293892 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7cdb007c8bc96863db1e9a9fbef9315b4db8f93dc6284b24e3e0e3bc9d00528a | 34.864118293892 | 6028 of 0 | <e0> |
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": 4855,
"vin": [ {
"gen": {
"height": 4795
}
}
],
"vout": [ {
"amount": 34864118293892,
"target": {
"tagged_key": {
"key": "7cdb007c8bc96863db1e9a9fbef9315b4db8f93dc6284b24e3e0e3bc9d00528a",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 0, 74, 60, 84, 121, 30, 119, 208, 126, 49, 230, 189, 195, 193, 251, 212, 142, 212, 170, 11, 180, 188, 128, 104, 91, 139, 210, 14, 42, 228, 63, 193, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}