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: 5a932e9f2c457701f7ab81c96acf9a878ae743a8a6255296fa5090e1e6e43bb4
Tx prefix hash: 83e63e979e50983ec7323bbbe80d5f094dd8ea3b60dbd2adf70528863280a1d7
Tx public key: 5bb4e134792141287369c3e347f353c927572e738a6a4c602ba2d47e1f10354a
| Timestamp: 1780686653 | Timestamp [UTC]: 2026-06-05 19:10:53 | Age [y:d:h:m:s]: 00:003:08:27:57 |
| Block: 5441 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2509 | RingCT/type: yes/0 |
| Extra: 015bb4e134792141287369c3e347f353c927572e738a6a4c602ba2d47e1f10354a020900000001e49593ff00 | ||
1 output(s) for total of 34.821186980908 HMNY
| stealth address | amount | amount idx | tag |
| 00: 932988c6ed0976f37e01e33447ca7808d81b2acce3e46bf3853373dfb2c1427b | 34.821186980908 | 6880 of 0 | <82> |
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": 5501,
"vin": [ {
"gen": {
"height": 5441
}
}
],
"vout": [ {
"amount": 34821186980908,
"target": {
"tagged_key": {
"key": "932988c6ed0976f37e01e33447ca7808d81b2acce3e46bf3853373dfb2c1427b",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 91, 180, 225, 52, 121, 33, 65, 40, 115, 105, 195, 227, 71, 243, 83, 201, 39, 87, 46, 115, 138, 106, 76, 96, 43, 162, 212, 126, 31, 16, 53, 74, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}