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: 290e0933a2f6bae624b385e52da0504894186f9140c4dd816a52ab3c6c665b70
Tx prefix hash: 1d0c4b6435e331cd59075e93be73a29872e9771ec5a8ebab90ee9473729f24c4
Tx public key: 19a4e1584dc9c8b8b212e184a3948c27a63508591f2ffa9573ada2d959ffc2eb
| Timestamp: 1780323348 | Timestamp [UTC]: 2026-06-01 14:15:48 | Age [y:d:h:m:s]: 00:007:12:34:00 |
| Block: 5115 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2784 | RingCT/type: yes/0 |
| Extra: 0119a4e1584dc9c8b8b212e184a3948c27a63508591f2ffa9573ada2d959ffc2eb02090000004026697be300 | ||
1 output(s) for total of 34.842845397162 HMNY
| stealth address | amount | amount idx | tag |
| 00: d67f27a7648b78a283db015da71abedfd53930d28f6027c0594500d1f92e1541 | 34.842845397162 | 6490 of 0 | <92> |
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": 5175,
"vin": [ {
"gen": {
"height": 5115
}
}
],
"vout": [ {
"amount": 34842845397162,
"target": {
"tagged_key": {
"key": "d67f27a7648b78a283db015da71abedfd53930d28f6027c0594500d1f92e1541",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 25, 164, 225, 88, 77, 201, 200, 184, 178, 18, 225, 132, 163, 148, 140, 39, 166, 53, 8, 89, 31, 47, 250, 149, 115, 173, 162, 217, 89, 255, 194, 235, 2, 9, 0, 0, 0, 64, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}