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: b97b34381b358611512e4f556127405a1b053794d21693e72fb1f172335db1ca
Tx prefix hash: 04f7977c75a2a4371ee069469a776b8b13b415f1f4894d181fd6be22384dcc5f
Tx public key: 7cd1bd44e6491c5b4a7408820edc341347e851627bc2c5210e88f870f48ed21c
| Timestamp: 1780985761 | Timestamp [UTC]: 2026-06-09 06:16:01 | Age [y:d:h:m:s]: 00:000:09:43:43 |
| Block: 8138 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 553 | RingCT/type: yes/0 |
| Extra: 017cd1bd44e6491c5b4a7408820edc341347e851627bc2c5210e88f870f48ed21c020900000001e49593ff00 | ||
1 output(s) for total of 34.642522401758 HMNY
| stealth address | amount | amount idx | tag |
| 00: a3abeaa1a06d7229ef01cca18af8157a07c99975165b9099632f32056c22c0be | 34.642522401758 | 10078 of 0 | <8c> |
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": 8198,
"vin": [ {
"gen": {
"height": 8138
}
}
],
"vout": [ {
"amount": 34642522401758,
"target": {
"tagged_key": {
"key": "a3abeaa1a06d7229ef01cca18af8157a07c99975165b9099632f32056c22c0be",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 124, 209, 189, 68, 230, 73, 28, 91, 74, 116, 8, 130, 14, 220, 52, 19, 71, 232, 81, 98, 123, 194, 197, 33, 14, 136, 248, 112, 244, 142, 210, 28, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}