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: 3836e1ba3a4be6d7c80962a850f69ed5a05365fa1cde9ca59197e7e0a0c875e8
Tx prefix hash: e429cfc47ef221127462a6ad83b6ff3223c5e85782a5b58e94def07910c90bfa
Tx public key: 7053035caf3cb55379998910e1ad566313dba38ba2d2b88b7c34900e6c757058
| Timestamp: 1781019390 | Timestamp [UTC]: 2026-06-09 15:36:30 | Age [y:d:h:m:s]: 00:006:06:00:54 |
| Block: 8671 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 74 | RingCT/type: yes/0 |
| Extra: 017053035caf3cb55379998910e1ad566313dba38ba2d2b88b7c34900e6c757058020900000001e49593ff00 | ||
1 output(s) for total of 34.607322092828 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ed2ee7a0e9078a20ac90b64ff21233c9eedd1557cff740d951eac946a04ec39 | 34.607322092828 | 10721 of 0 | <a4> |
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": 8731,
"vin": [ {
"gen": {
"height": 8671
}
}
],
"vout": [ {
"amount": 34607322092828,
"target": {
"tagged_key": {
"key": "4ed2ee7a0e9078a20ac90b64ff21233c9eedd1557cff740d951eac946a04ec39",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 112, 83, 3, 92, 175, 60, 181, 83, 121, 153, 137, 16, 225, 173, 86, 99, 19, 219, 163, 139, 162, 210, 184, 139, 124, 52, 144, 14, 108, 117, 112, 88, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}