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: e48f39b2049ef1bf41d5bce5ff18bc8c3cf20a2df85d023d72383f2d0f825580
Tx prefix hash: c01c1389a8ddd04e8cd4ec092d316fc4ce10317bbb292cfe771679171869f49b
Tx public key: 667d51aa54dfbe78d29c3a19567ef2f29a5dbd3877be3942040a8bc08ce45706
| Timestamp: 1781019707 | Timestamp [UTC]: 2026-06-09 15:41:47 | Age [y:d:h:m:s]: 00:009:15:59:50 |
| Block: 8677 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 68 | RingCT/type: yes/0 |
| Extra: 01667d51aa54dfbe78d29c3a19567ef2f29a5dbd3877be3942040a8bc08ce45706020900000001e49593ff00 | ||
1 output(s) for total of 34.606926045345 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b3f5c5e4df427dbdbbb54e0f26a82a3d710479083e69669b1a9ffe1da872016 | 34.606926045345 | 10729 of 0 | <e2> |
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": 8737,
"vin": [ {
"gen": {
"height": 8677
}
}
],
"vout": [ {
"amount": 34606926045345,
"target": {
"tagged_key": {
"key": "2b3f5c5e4df427dbdbbb54e0f26a82a3d710479083e69669b1a9ffe1da872016",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 102, 125, 81, 170, 84, 223, 190, 120, 210, 156, 58, 25, 86, 126, 242, 242, 154, 93, 189, 56, 119, 190, 57, 66, 4, 10, 139, 192, 140, 228, 87, 6, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}