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: b46ec550368d34d9b6bdbf10b17702577dbd0a4e362d9d0c067860328f276c03
Tx prefix hash: 142a0e6e05957db4e6d55dd4ea8f7cb6dda9e07fe97c4ee5793d58b1bbe11f50
Tx public key: 94d3a9080b019595a6a389fd7cc9dbd31f6d515a51f99c8f1f5689339126ba4c
| Timestamp: 1780864980 | Timestamp [UTC]: 2026-06-07 20:43:00 | Age [y:d:h:m:s]: 00:001:01:41:49 |
| Block: 7653 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 233 | RingCT/type: yes/0 |
| Extra: 0194d3a9080b019595a6a389fd7cc9dbd31f6d515a51f99c8f1f5689339126ba4c020900000001e49593ff00 | ||
1 output(s) for total of 34.674583812832 HMNY
| stealth address | amount | amount idx | tag |
| 00: a09f3e5c36cf879abb22aa3b6c623315774df3ea339681b77c136a0ef6d8c512 | 34.674583812832 | 9463 of 0 | <49> |
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": 7713,
"vin": [ {
"gen": {
"height": 7653
}
}
],
"vout": [ {
"amount": 34674583812832,
"target": {
"tagged_key": {
"key": "a09f3e5c36cf879abb22aa3b6c623315774df3ea339681b77c136a0ef6d8c512",
"view_tag": "49"
}
}
}
],
"extra": [ 1, 148, 211, 169, 8, 11, 1, 149, 149, 166, 163, 137, 253, 124, 201, 219, 211, 31, 109, 81, 90, 81, 249, 156, 143, 31, 86, 137, 51, 145, 38, 186, 76, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}