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: 7a5e646823b8b9c6310d12732193bac7e4a86bd342c89ec2711604726c736abf
Tx prefix hash: f951fcc6fac0443605a9251ee449ea4531915d7b06c02326b1343d28a02a7be1
Tx public key: 61df0040ad183a6dc8da9799a1123a4e2667ffc4e62ee0b9832f7be116d62051
| Timestamp: 1779737333 | Timestamp [UTC]: 2026-05-25 19:28:53 | Age [y:d:h:m:s]: 00:014:07:20:55 |
| Block: 1922 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5987 | RingCT/type: yes/0 |
| Extra: 0161df0040ad183a6dc8da9799a1123a4e2667ffc4e62ee0b9832f7be116d6205102090000000626697be300 | ||
1 output(s) for total of 35.058299325944 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2ba8f42c47c4f9149d8406e427fb112d36135f042ff0a189950e15e8680e0158 | 35.058299325944 | 2160 of 0 | <4e> |
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": 1982,
"vin": [ {
"gen": {
"height": 1922
}
}
],
"vout": [ {
"amount": 35058299325944,
"target": {
"tagged_key": {
"key": "2ba8f42c47c4f9149d8406e427fb112d36135f042ff0a189950e15e8680e0158",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 97, 223, 0, 64, 173, 24, 58, 109, 200, 218, 151, 153, 161, 18, 58, 78, 38, 103, 255, 196, 230, 46, 224, 185, 131, 47, 123, 225, 22, 214, 32, 81, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}