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: f23fd9d427a67c062ea9047b66ada30af970163fbc9d72f285b0813581e8addf
Tx prefix hash: 9ae67266576633bd94d7b70d9a84ef5d2bdea532fa31ab65ed9d92c4180de271
Tx public key: c40a63fcc408e8600dd4a3a2a7638a536f0fe26c74e1442021789f7a3cd58349
| Timestamp: 1779724795 | Timestamp [UTC]: 2026-05-25 15:59:55 | Age [y:d:h:m:s]: 00:014:10:40:41 |
| Block: 1836 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6060 | RingCT/type: yes/0 |
| Extra: 01c40a63fcc408e8600dd4a3a2a7638a536f0fe26c74e1442021789f7a3cd58349020900000002ba6d17be00 | ||
1 output(s) for total of 35.061442457676 HMNY
| stealth address | amount | amount idx | tag |
| 00: dcbde8ccd2e81a29235d236cb4f416633a1de3b77f46343fd9f4931176b849a5 | 35.061442457676 | 2032 of 0 | <47> |
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": 1896,
"vin": [ {
"gen": {
"height": 1836
}
}
],
"vout": [ {
"amount": 35061442457676,
"target": {
"tagged_key": {
"key": "dcbde8ccd2e81a29235d236cb4f416633a1de3b77f46343fd9f4931176b849a5",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 196, 10, 99, 252, 196, 8, 232, 96, 13, 212, 163, 162, 167, 99, 138, 83, 111, 15, 226, 108, 116, 225, 68, 32, 33, 120, 159, 122, 60, 213, 131, 73, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}