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: 6c57a37d9680c8b1a8ec1a3596ad56bd9642cee745cdf7d46540924908d80516
Tx prefix hash: 3dd0f946b6ddde5b2c534ef25ad30d9e617cc68a8bf728147fa09bf4efd3c415
Tx public key: 4843012807770c85fef0f7f53e45834ea734ba71e9e58207e90c4acf8166e6f6
| Timestamp: 1780982890 | Timestamp [UTC]: 2026-06-09 05:28:10 | Age [y:d:h:m:s]: 00:000:08:09:26 |
| Block: 8075 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 526 | RingCT/type: yes/0 |
| Extra: 014843012807770c85fef0f7f53e45834ea734ba71e9e58207e90c4acf8166e6f6020900000001e49593ff00 | ||
1 output(s) for total of 34.646685404010 HMNY
| stealth address | amount | amount idx | tag |
| 00: fcb92efd204a61f01a76d742ecc2fabe38c4846bcabe02132e1be5704431d921 | 34.646685404010 | 10005 of 0 | <8a> |
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": 8135,
"vin": [ {
"gen": {
"height": 8075
}
}
],
"vout": [ {
"amount": 34646685404010,
"target": {
"tagged_key": {
"key": "fcb92efd204a61f01a76d742ecc2fabe38c4846bcabe02132e1be5704431d921",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 72, 67, 1, 40, 7, 119, 12, 133, 254, 240, 247, 245, 62, 69, 131, 78, 167, 52, 186, 113, 233, 229, 130, 7, 233, 12, 74, 207, 129, 102, 230, 246, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}