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: ecb90d1638d6e2ef35de534cc6f10311aaf4b5e463916694823c60ebe9b0c238
Tx prefix hash: 0aca1e71b382388374e590e1bf33d5b05af131cf0dc9f88fe5a64d87e618a243
Tx public key: 840668b52ecbfb7fcb86800e1b34627d6168e6bc7deea7e410c19f5be6ff7f2c
| Timestamp: 1779916988 | Timestamp [UTC]: 2026-05-27 21:23:08 | Age [y:d:h:m:s]: 00:012:03:23:39 |
| Block: 3320 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4566 | RingCT/type: yes/0 |
| Extra: 01840668b52ecbfb7fcb86800e1b34627d6168e6bc7deea7e410c19f5be6ff7f2c02090000000126697be300 | ||
1 output(s) for total of 34.962341081625 HMNY
| stealth address | amount | amount idx | tag |
| 00: d583c34ab059680d2c00b4e7651159462094db1179e11a7b261a9260a38698c6 | 34.962341081625 | 3988 of 0 | <1e> |
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": 3380,
"vin": [ {
"gen": {
"height": 3320
}
}
],
"vout": [ {
"amount": 34962341081625,
"target": {
"tagged_key": {
"key": "d583c34ab059680d2c00b4e7651159462094db1179e11a7b261a9260a38698c6",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 132, 6, 104, 181, 46, 203, 251, 127, 203, 134, 128, 14, 27, 52, 98, 125, 97, 104, 230, 188, 125, 238, 167, 228, 16, 193, 159, 91, 230, 255, 127, 44, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}