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: 81e0cb7b9ecb7e5d7063c98b74a167b243ac47e2b9d20400f80a16ad6c20d4f5
Tx prefix hash: 7df2950e6510ba03f5e781bc8f5fc2a50b319a4b3d11f8fb5abde5fe83c67f77
Tx public key: 298c015c73e1ecfd6f4f6b27da059820c475ea46abd6c0c35f9434d9d903f870
| Timestamp: 1779996552 | Timestamp [UTC]: 2026-05-28 19:29:12 | Age [y:d:h:m:s]: 00:011:08:09:38 |
| Block: 4031 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3916 | RingCT/type: yes/0 |
| Extra: 01298c015c73e1ecfd6f4f6b27da059820c475ea46abd6c0c35f9434d9d903f87002090000000226697be300 | ||
1 output(s) for total of 34.917577070588 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8d24649e0801968ca71a6eb237020782d465f0aecd05db4da882613af0b81de3 | 34.917577070588 | 4988 of 0 | <95> |
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": 4091,
"vin": [ {
"gen": {
"height": 4031
}
}
],
"vout": [ {
"amount": 34917577070588,
"target": {
"tagged_key": {
"key": "8d24649e0801968ca71a6eb237020782d465f0aecd05db4da882613af0b81de3",
"view_tag": "95"
}
}
}
],
"extra": [ 1, 41, 140, 1, 92, 115, 225, 236, 253, 111, 79, 107, 39, 218, 5, 152, 32, 196, 117, 234, 70, 171, 214, 192, 195, 95, 148, 52, 217, 217, 3, 248, 112, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}