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: a8847676361ecc512bfdde1bdd0ebcee14cb456d9667c83987f6196f744aadc1
Tx prefix hash: 9e69c08b59b00c3fff2dab9dec0d020e01f021321ec244697e22753ae0f14150
Tx public key: 235c0ae895ea902a019d67fd351d96832118fa5b58d5d51c72808d1a6d58edeb
| Timestamp: 1779848072 | Timestamp [UTC]: 2026-05-27 02:14:32 | Age [y:d:h:m:s]: 00:013:00:26:04 |
| Block: 2491 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5405 | RingCT/type: yes/0 |
| Extra: 01235c0ae895ea902a019d67fd351d96832118fa5b58d5d51c72808d1a6d58edeb02090000000126697be300 | ||
1 output(s) for total of 35.017667037941 HMNY
| stealth address | amount | amount idx | tag |
| 00: 71b709b97da3be6a3a42813bfc734c67eea69f4b6a294b0c96279cc483ec4f9f | 35.017667037941 | 2929 of 0 | <a6> |
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": 2551,
"vin": [ {
"gen": {
"height": 2491
}
}
],
"vout": [ {
"amount": 35017667037941,
"target": {
"tagged_key": {
"key": "71b709b97da3be6a3a42813bfc734c67eea69f4b6a294b0c96279cc483ec4f9f",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 35, 92, 10, 232, 149, 234, 144, 42, 1, 157, 103, 253, 53, 29, 150, 131, 33, 24, 250, 91, 88, 213, 213, 28, 114, 128, 141, 26, 109, 88, 237, 235, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}