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: 34fd262565f3ea3cd149f5d8b52f1d2a18c470141bba712b5c8acbf8a6a2cd57
Tx prefix hash: ef90b30972e915d607800339e132b758f090f2c91ba475cef727d21ad3281574
Tx public key: c956418def4f400aa34f0c8d61d0a8e6f7ce485f9eadf3d9a019413189ee79ae
| Timestamp: 1779994051 | Timestamp [UTC]: 2026-05-28 18:47:31 | Age [y:d:h:m:s]: 00:011:06:48:26 |
| Block: 4012 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3874 | RingCT/type: yes/0 |
| Extra: 01c956418def4f400aa34f0c8d61d0a8e6f7ce485f9eadf3d9a019413189ee79ae02090000000426697be300 | ||
1 output(s) for total of 34.916225199741 HMNY
| stealth address | amount | amount idx | tag |
| 00: 699f02f6285e9b4eb624daf243c0d65eaccba7e5c91cccbf68cf50ccc67d57c0 | 34.916225199741 | 4961 of 0 | <f9> |
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": 4072,
"vin": [ {
"gen": {
"height": 4012
}
}
],
"vout": [ {
"amount": 34916225199741,
"target": {
"tagged_key": {
"key": "699f02f6285e9b4eb624daf243c0d65eaccba7e5c91cccbf68cf50ccc67d57c0",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 201, 86, 65, 141, 239, 79, 64, 10, 163, 79, 12, 141, 97, 208, 168, 230, 247, 206, 72, 95, 158, 173, 243, 217, 160, 25, 65, 49, 137, 238, 121, 174, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}