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: ab3f0e1cdc42b9747a0eb05fc7451f9ff6e302e05e36f4620ebb6dba6ade3501
Tx prefix hash: db679bc500562711f343144dccb32a5fc35fabe81fd7c839e1dc6f06da5ae86a
Tx public key: dd00cc9f90ae48279afd9fd315ddf77f8ee5506a2ca498dda637283abfdac43f
| Timestamp: 1780688087 | Timestamp [UTC]: 2026-06-05 19:34:47 | Age [y:d:h:m:s]: 00:003:07:05:49 |
| Block: 5511 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2385 | RingCT/type: yes/0 |
| Extra: 01dd00cc9f90ae48279afd9fd315ddf77f8ee5506a2ca498dda637283abfdac43f020900000002e49593ff00 | ||
1 output(s) for total of 34.816538156787 HMNY
| stealth address | amount | amount idx | tag |
| 00: aab34fb8b8914afb43355183ed5492bff16d63c2a17b4d4fcba0f2a2c81a4d39 | 34.816538156787 | 6952 of 0 | <16> |
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": 5571,
"vin": [ {
"gen": {
"height": 5511
}
}
],
"vout": [ {
"amount": 34816538156787,
"target": {
"tagged_key": {
"key": "aab34fb8b8914afb43355183ed5492bff16d63c2a17b4d4fcba0f2a2c81a4d39",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 221, 0, 204, 159, 144, 174, 72, 39, 154, 253, 159, 211, 21, 221, 247, 127, 142, 229, 80, 106, 44, 164, 152, 221, 166, 55, 40, 58, 191, 218, 196, 63, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}