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: 1d8961ce31a7bd5e67f6d366604e2fbdb9dface63e4647a94c4d87643f4d8fda
Tx prefix hash: 0f3ce717d08faee30216fdd2d956112b6662b7a1f2626e1db70c43f1f66aba7e
Tx public key: afd9c15170c1d238eeea4b87f0a4843c599e09d4da1c543049b7dfc3b51450b7
| Timestamp: 1780049292 | Timestamp [UTC]: 2026-05-29 10:08:12 | Age [y:d:h:m:s]: 00:015:01:12:53 |
| Block: 4376 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4369 | RingCT/type: yes/0 |
| Extra: 01afd9c15170c1d238eeea4b87f0a4843c599e09d4da1c543049b7dfc3b51450b702090000000726697be300 | ||
1 output(s) for total of 34.891992130968 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75c55712557410a138f7d82fef2da92f727049085972b4507b4153cac843921f | 34.891992130968 | 5473 of 0 | <94> |
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": 4436,
"vin": [ {
"gen": {
"height": 4376
}
}
],
"vout": [ {
"amount": 34891992130968,
"target": {
"tagged_key": {
"key": "75c55712557410a138f7d82fef2da92f727049085972b4507b4153cac843921f",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 175, 217, 193, 81, 112, 193, 210, 56, 238, 234, 75, 135, 240, 164, 132, 60, 89, 158, 9, 212, 218, 28, 84, 48, 73, 183, 223, 195, 181, 20, 80, 183, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}