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: dcc8522f4c0b1ec51b5ca56cd40ed0e41c50dcf5e5839b9fcc8e1d48f0be56e8
Tx prefix hash: bbedadde26f253444e469f70b1561a828e1c4c1da37a8819ae2cb683f8dcef4b
Tx public key: d6dc4f985c2a8618420423d84b6714c0a7556f35170eca4b3f01e2c306e1b7e3
| Timestamp: 1779842506 | Timestamp [UTC]: 2026-05-27 00:41:46 | Age [y:d:h:m:s]: 00:013:00:05:01 |
| Block: 2410 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5476 | RingCT/type: yes/0 |
| Extra: 01d6dc4f985c2a8618420423d84b6714c0a7556f35170eca4b3f01e2c306e1b7e302090000000226697be300 | ||
1 output(s) for total of 35.023077523884 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7df62f6b76a62f75ca94869ef1cf67d39c9c05cc638054f50b4033ce098eaf43 | 35.023077523884 | 2830 of 0 | <89> |
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": 2470,
"vin": [ {
"gen": {
"height": 2410
}
}
],
"vout": [ {
"amount": 35023077523884,
"target": {
"tagged_key": {
"key": "7df62f6b76a62f75ca94869ef1cf67d39c9c05cc638054f50b4033ce098eaf43",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 214, 220, 79, 152, 92, 42, 134, 24, 66, 4, 35, 216, 75, 103, 20, 192, 167, 85, 111, 53, 23, 14, 202, 75, 63, 1, 226, 195, 6, 225, 183, 227, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}