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: dd0f0596abc28143639af76ee32051000eca04a44cf7d03196b52d04be883f07
Tx prefix hash: 3fc2f43658246e6bc2197d99c869dbedb75b3adbf4d0f218904e65491664e9c8
Tx public key: ec16c1b21d76a8bd85765a70a64fcd9e24a80492661f69b614c8429aee5c46c3
| Timestamp: 1779713929 | Timestamp [UTC]: 2026-05-25 12:58:49 | Age [y:d:h:m:s]: 00:014:12:37:08 |
| Block: 1606 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6280 | RingCT/type: yes/0 |
| Extra: 01ec16c1b21d76a8bd85765a70a64fcd9e24a80492661f69b614c8429aee5c46c3020900000003ba6d17be00 | ||
1 output(s) for total of 35.076826957313 HMNY
| stealth address | amount | amount idx | tag |
| 00: 905063457ac11a56efa3edfb4ff17f9d0569ec6f716a02644e51b4120355eab7 | 35.076826957313 | 1764 of 0 | <43> |
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": 1666,
"vin": [ {
"gen": {
"height": 1606
}
}
],
"vout": [ {
"amount": 35076826957313,
"target": {
"tagged_key": {
"key": "905063457ac11a56efa3edfb4ff17f9d0569ec6f716a02644e51b4120355eab7",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 236, 22, 193, 178, 29, 118, 168, 189, 133, 118, 90, 112, 166, 79, 205, 158, 36, 168, 4, 146, 102, 31, 105, 182, 20, 200, 66, 154, 238, 92, 70, 195, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}