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: b8b5db13b8da97390d9b23d06f133cb04562871f677e68fd6d870654fa5cec4b
Tx prefix hash: 1e3a72fec068bff523989852e797e27cb77366f5ab7d971cb73ea0e12d9e282c
Tx public key: 40d399aaa101c20ee883ede5cab8fc60f796af4a8286ac928e48b6b06f6c83b8
| Timestamp: 1780982771 | Timestamp [UTC]: 2026-06-09 05:26:11 | Age [y:d:h:m:s]: 00:000:07:11:34 |
| Block: 8071 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 501 | RingCT/type: yes/0 |
| Extra: 0140d399aaa101c20ee883ede5cab8fc60f796af4a8286ac928e48b6b06f6c83b8020900000002e49593ff00 | ||
1 output(s) for total of 34.646949738503 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30e776eb5f29b5f5cd4a6922669ab0754a4247a9705d46f9ec31f4ce0d150e6a | 34.646949738503 | 10001 of 0 | <9d> |
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": 8131,
"vin": [ {
"gen": {
"height": 8071
}
}
],
"vout": [ {
"amount": 34646949738503,
"target": {
"tagged_key": {
"key": "30e776eb5f29b5f5cd4a6922669ab0754a4247a9705d46f9ec31f4ce0d150e6a",
"view_tag": "9d"
}
}
}
],
"extra": [ 1, 64, 211, 153, 170, 161, 1, 194, 14, 232, 131, 237, 229, 202, 184, 252, 96, 247, 150, 175, 74, 130, 134, 172, 146, 142, 72, 182, 176, 111, 108, 131, 184, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}