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: fa4b5e4f95f4581b9341ec137c33041f604c98235a88352dbc1a87b76788061e
Tx prefix hash: 43d00794dd838846bbf7efe23cf785abe03b6697b4345bc431a334e0b084865f
Tx public key: a743a98f3ea8ae0dc485e427c0210cc11a870da9766d0420e39d05bd64c54650
| Timestamp: 1779803294 | Timestamp [UTC]: 2026-05-26 13:48:14 | Age [y:d:h:m:s]: 00:013:10:58:33 |
| Block: 2321 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5565 | RingCT/type: yes/0 |
| Extra: 01a743a98f3ea8ae0dc485e427c0210cc11a870da9766d0420e39d05bd64c5465002090000000326697be300 | ||
1 output(s) for total of 35.033231742698 HMNY
| stealth address | amount | amount idx | tag |
| 00: 48f62b6fba6b7ece4c817e7a9ea871087398307c94d51e6f80eb44f62b99bfb9 | 35.033231742698 | 2713 of 0 | <b2> |
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": 2381,
"vin": [ {
"gen": {
"height": 2321
}
}
],
"vout": [ {
"amount": 35033231742698,
"target": {
"tagged_key": {
"key": "48f62b6fba6b7ece4c817e7a9ea871087398307c94d51e6f80eb44f62b99bfb9",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 167, 67, 169, 143, 62, 168, 174, 13, 196, 133, 228, 39, 192, 33, 12, 193, 26, 135, 13, 169, 118, 109, 4, 32, 227, 157, 5, 189, 100, 197, 70, 80, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}