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: c7008c56fdf692ffbafc3bf461af4db59664d24a7924f81b0507e96894bf183e
Tx prefix hash: d062122913b12b04e4277921468b9b3ae72591b3c44bbf9695855492ab922a2e
Tx public key: 41d9ab015dfd234aec653ff4820c9d3a1a06fae6859627b4e85a2dfe681e72ad
| Timestamp: 1780725378 | Timestamp [UTC]: 2026-06-06 05:56:18 | Age [y:d:h:m:s]: 00:002:20:44:18 |
| Block: 6268 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1628 | RingCT/type: yes/0 |
| Extra: 0141d9ab015dfd234aec653ff4820c9d3a1a06fae6859627b4e85a2dfe681e72ad020900000001e49593ff00 | ||
1 output(s) for total of 34.766304074897 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a75181958f5a544d0658a7a9af61151da1b53a3d88ecbb668acb9893b6119cc | 34.766304074897 | 7751 of 0 | <48> |
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": 6328,
"vin": [ {
"gen": {
"height": 6268
}
}
],
"vout": [ {
"amount": 34766304074897,
"target": {
"tagged_key": {
"key": "5a75181958f5a544d0658a7a9af61151da1b53a3d88ecbb668acb9893b6119cc",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 65, 217, 171, 1, 93, 253, 35, 74, 236, 101, 63, 244, 130, 12, 157, 58, 26, 6, 250, 230, 133, 150, 39, 180, 232, 90, 45, 254, 104, 30, 114, 173, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}