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: 379dd975ac2f1684ccdd0e948f7ea67ccdd9428c5b071010e860cb883e518c2c
Tx prefix hash: 4bde6ef6b67d16f821dade066b8c72c13e6ac9a43f28580cad46a74af84e2470
Tx public key: 318c500fb54d234f55d10db478535b4e562f6a797c4661ce935a7c61ac4dcae5
| Timestamp: 1779453858 | Timestamp [UTC]: 2026-05-22 12:44:18 | Age [y:d:h:m:s]: 00:025:19:44:54 |
| Block: 359 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8386 | RingCT/type: yes/0 |
| Extra: 01318c500fb54d234f55d10db478535b4e562f6a797c4661ce935a7c61ac4dcae502090000000493369e7d00 | ||
1 output(s) for total of 35.160355293366 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7dde50445c4e22c2c61856e9e0d312bc868be6789ae97e173f5c025b6efb0aa | 35.160355293366 | 355 of 0 | <17> |
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": 419,
"vin": [ {
"gen": {
"height": 359
}
}
],
"vout": [ {
"amount": 35160355293366,
"target": {
"tagged_key": {
"key": "b7dde50445c4e22c2c61856e9e0d312bc868be6789ae97e173f5c025b6efb0aa",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 49, 140, 80, 15, 181, 77, 35, 79, 85, 209, 13, 180, 120, 83, 91, 78, 86, 47, 106, 121, 124, 70, 97, 206, 147, 90, 124, 97, 172, 77, 202, 229, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}