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: 3a0e45eadd399fbcfb0b53713690f0dd5f553ad4b9699c85e3d95f08145fb975
Tx prefix hash: e6e8aee943b54bf554095d6a09986159f4e2ea960052066151fc6e2160e667d1
Tx public key: 7f1c8a29b72eeb0e76c932b6e90eecb993d03d16985830605c30c087f119db7b
| Timestamp: 1779722501 | Timestamp [UTC]: 2026-05-25 15:21:41 | Age [y:d:h:m:s]: 00:014:10:14:16 |
| Block: 1779 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6107 | RingCT/type: yes/0 |
| Extra: 017f1c8a29b72eeb0e76c932b6e90eecb993d03d16985830605c30c087f119db7b020900000001ba6d17be00 | ||
1 output(s) for total of 35.065254509006 HMNY
| stealth address | amount | amount idx | tag |
| 00: 80dc6b8eb883bd136486d572e88eead0caa39cf5cc90d37b8fbadec25712465d | 35.065254509006 | 1966 of 0 | <3e> |
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": 1839,
"vin": [ {
"gen": {
"height": 1779
}
}
],
"vout": [ {
"amount": 35065254509006,
"target": {
"tagged_key": {
"key": "80dc6b8eb883bd136486d572e88eead0caa39cf5cc90d37b8fbadec25712465d",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 127, 28, 138, 41, 183, 46, 235, 14, 118, 201, 50, 182, 233, 14, 236, 185, 147, 208, 61, 22, 152, 88, 48, 96, 92, 48, 192, 135, 241, 25, 219, 123, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}