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: 4e544c40af74f1aa1db23729e199083a763f735dacd698757fa1775a4a02c1af
Tx prefix hash: 1485e5ce028763ca831e5a8e4d704af23c2ba9548e4df33ba29b979f31b6e752
Tx public key: 104e63a064bfaa41b13a2ff8af6168a4f5df7629e3d4ef1bb05e8a0c24e7dc4a
| Timestamp: 1779840060 | Timestamp [UTC]: 2026-05-27 00:01:00 | Age [y:d:h:m:s]: 00:013:02:39:36 |
| Block: 2376 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5521 | RingCT/type: yes/0 |
| Extra: 01104e63a064bfaa41b13a2ff8af6168a4f5df7629e3d4ef1bb05e8a0c24e7dc4a02090000000126697be300 | ||
1 output(s) for total of 35.025348841144 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5ead1f584343852b59f47707369e066aa9903b0060092881e22a7a3e1cd2f1ea | 35.025348841144 | 2788 of 0 | <7e> |
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": 2436,
"vin": [ {
"gen": {
"height": 2376
}
}
],
"vout": [ {
"amount": 35025348841144,
"target": {
"tagged_key": {
"key": "5ead1f584343852b59f47707369e066aa9903b0060092881e22a7a3e1cd2f1ea",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 16, 78, 99, 160, 100, 191, 170, 65, 177, 58, 47, 248, 175, 97, 104, 164, 245, 223, 118, 41, 227, 212, 239, 27, 176, 94, 138, 12, 36, 231, 220, 74, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}