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: 4dc1b08132ba769d1dd4b276e38e44490e2ce85337caa88c0ac8dfdb9af67695
Tx prefix hash: 383138dfe7d7436e6dffe3e7d6a511ca26417013eb71894609435732a6099fdb
Tx public key: e9cf7e7db82157639f5ba384b606ecb2eda90dda9ab2fea14eb68d797c3815e7
| Timestamp: 1779903565 | Timestamp [UTC]: 2026-05-27 17:39:25 | Age [y:d:h:m:s]: 00:012:07:56:32 |
| Block: 3174 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4712 | RingCT/type: yes/0 |
| Extra: 01e9cf7e7db82157639f5ba384b606ecb2eda90dda9ab2fea14eb68d797c3815e702090000000126697be300 | ||
1 output(s) for total of 34.972078511179 HMNY
| stealth address | amount | amount idx | tag |
| 00: cd7354e931b3f5511f4fdc8f9c2bf8b4c6a655d2d47cb9de2977c134be8a087a | 34.972078511179 | 3798 of 0 | <d6> |
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": 3234,
"vin": [ {
"gen": {
"height": 3174
}
}
],
"vout": [ {
"amount": 34972078511179,
"target": {
"tagged_key": {
"key": "cd7354e931b3f5511f4fdc8f9c2bf8b4c6a655d2d47cb9de2977c134be8a087a",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 233, 207, 126, 125, 184, 33, 87, 99, 159, 91, 163, 132, 182, 6, 236, 178, 237, 169, 13, 218, 154, 178, 254, 161, 78, 182, 141, 121, 124, 56, 21, 231, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}