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: 49d7429fdc2f5a69c2c9f3d911cc2d15d54dc4a5442231c5105bb2404fdd1dab
Tx prefix hash: 0a7c17fca7e4e5e3cc2b03c5822674907b19f4b31826dea736063d0c668edf05
Tx public key: abba4d6def664845c518cb7a35dd4a959f8d91a4d0516a374d74837424613877
| Timestamp: 1780774149 | Timestamp [UTC]: 2026-06-06 19:29:09 | Age [y:d:h:m:s]: 00:002:06:06:48 |
| Block: 6697 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1189 | RingCT/type: yes/0 |
| Extra: 01abba4d6def664845c518cb7a35dd4a959f8d91a4d0516a374d74837424613877020900000001e49593ff00 | ||
1 output(s) for total of 34.737868065851 HMNY
| stealth address | amount | amount idx | tag |
| 00: 12e76730d55c425ecb28c3f2d2f77b55ddbf2d26c270b6ab64a255729c2069a7 | 34.737868065851 | 8259 of 0 | <e5> |
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": 6757,
"vin": [ {
"gen": {
"height": 6697
}
}
],
"vout": [ {
"amount": 34737868065851,
"target": {
"tagged_key": {
"key": "12e76730d55c425ecb28c3f2d2f77b55ddbf2d26c270b6ab64a255729c2069a7",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 171, 186, 77, 109, 239, 102, 72, 69, 197, 24, 203, 122, 53, 221, 74, 149, 159, 141, 145, 164, 208, 81, 106, 55, 77, 116, 131, 116, 36, 97, 56, 119, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}