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: b3e157afa74a2ab0d348059ffcbacbed9223e1ec6e8ddbcfc8c625f7036d4a70
Tx prefix hash: 2da89868f3c471b0c295c8a935b84ddcedba0987281c2db17ce82db6d5d0e49e
Tx public key: d386997d177413a74af6a73ea8e2db5ff072d187b164b5189f2de8c4aa3c17cc
| Timestamp: 1780691947 | Timestamp [UTC]: 2026-06-05 20:39:07 | Age [y:d:h:m:s]: 00:003:06:10:41 |
| Block: 5763 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2156 | RingCT/type: yes/0 |
| Extra: 01d386997d177413a74af6a73ea8e2db5ff072d187b164b5189f2de8c4aa3c17cc020900000001e49593ff00 | ||
1 output(s) for total of 34.799807528292 HMNY
| stealth address | amount | amount idx | tag |
| 00: 410b1f265face6f179231986f4b172014f02817245c8aaddcc7ca3a136416cca | 34.799807528292 | 7216 of 0 | <28> |
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": 5823,
"vin": [ {
"gen": {
"height": 5763
}
}
],
"vout": [ {
"amount": 34799807528292,
"target": {
"tagged_key": {
"key": "410b1f265face6f179231986f4b172014f02817245c8aaddcc7ca3a136416cca",
"view_tag": "28"
}
}
}
],
"extra": [ 1, 211, 134, 153, 125, 23, 116, 19, 167, 74, 246, 167, 62, 168, 226, 219, 95, 240, 114, 209, 135, 177, 100, 181, 24, 159, 45, 232, 196, 170, 60, 23, 204, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}