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: 3f308d396a88b2d3017fee27d2a9532145f4c217a8a2baff17b5977288aff6af
Tx prefix hash: 681427180eb9f62d6bbfa26eca0114df09e377ea898de8551dbbde6fdf55b7ac
Tx public key: 364e614493f8eec85133d19fa746ea2d0be9c8999d3281f3cefefdc72476041f
| Timestamp: 1779629254 | Timestamp [UTC]: 2026-05-24 13:27:34 | Age [y:d:h:m:s]: 00:023:19:01:38 |
| Block: 822 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7923 | RingCT/type: yes/0 |
| Extra: 01364e614493f8eec85133d19fa746ea2d0be9c8999d3281f3cefefdc72476041f020900000001ba6d17be00 | ||
1 output(s) for total of 35.129318775255 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30d14c5b12f1398f9d46fe5770c3a7ab453f27168b509e0a7217de1eb89b9d54 | 35.129318775255 | 954 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": 882,
"vin": [ {
"gen": {
"height": 822
}
}
],
"vout": [ {
"amount": 35129318775255,
"target": {
"tagged_key": {
"key": "30d14c5b12f1398f9d46fe5770c3a7ab453f27168b509e0a7217de1eb89b9d54",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 54, 78, 97, 68, 147, 248, 238, 200, 81, 51, 209, 159, 167, 70, 234, 45, 11, 233, 200, 153, 157, 50, 129, 243, 206, 254, 253, 199, 36, 118, 4, 31, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}