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: c1e3c643194bb4a8ec27a7f2c8f6501566299298808d2e4ee2fdecd3b6f0018a
Tx prefix hash: b65714088d4d6c8d8aa42d93de63040d3f083769febd6607668a88ff5116c2cb
Tx public key: 23b586ea90c0acb59e9e3c960ffd3a15f4a0428c8bcaf415626f52618d73cf7e
| Timestamp: 1779950956 | Timestamp [UTC]: 2026-05-28 06:49:16 | Age [y:d:h:m:s]: 00:020:01:39:56 |
| Block: 3622 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5123 | RingCT/type: yes/0 |
| Extra: 0123b586ea90c0acb59e9e3c960ffd3a15f4a0428c8bcaf415626f52618d73cf7e02090000000726697be300 | ||
1 output(s) for total of 34.942207878752 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7b261eff20f4379b89949ad2e2fb78fe5cf2bcf2c77a9a4e0f65a138feb095e | 34.942207878752 | 4375 of 0 | <ed> |
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": 3682,
"vin": [ {
"gen": {
"height": 3622
}
}
],
"vout": [ {
"amount": 34942207878752,
"target": {
"tagged_key": {
"key": "b7b261eff20f4379b89949ad2e2fb78fe5cf2bcf2c77a9a4e0f65a138feb095e",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 35, 181, 134, 234, 144, 192, 172, 181, 158, 158, 60, 150, 15, 253, 58, 21, 244, 160, 66, 140, 139, 202, 244, 21, 98, 111, 82, 97, 141, 115, 207, 126, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}