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: 55874aca8a8b1360812f72a00cae4b14a73092369ee8cae162e04c157c0f727d
Tx prefix hash: 243c1a25ce437253d5c5e7c02f032f88be10396b6e8c466d14bd8d560ab920db
Tx public key: 448bc9d161a82e6cc4fadc2d4ec1f22a4086dcb449dc55b68778ada255098fff
| Timestamp: 1779910938 | Timestamp [UTC]: 2026-05-27 19:42:18 | Age [y:d:h:m:s]: 00:012:07:07:30 |
| Block: 3245 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4675 | RingCT/type: yes/0 |
| Extra: 01448bc9d161a82e6cc4fadc2d4ec1f22a4086dcb449dc55b68778ada255098fff02090000000226697be300 | ||
1 output(s) for total of 34.967342847150 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4140638a81e21c1316c5bed616d9201ef102dd7171558a5bae85ae44ad17e910 | 34.967342847150 | 3893 of 0 | <94> |
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": 3305,
"vin": [ {
"gen": {
"height": 3245
}
}
],
"vout": [ {
"amount": 34967342847150,
"target": {
"tagged_key": {
"key": "4140638a81e21c1316c5bed616d9201ef102dd7171558a5bae85ae44ad17e910",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 68, 139, 201, 209, 97, 168, 46, 108, 196, 250, 220, 45, 78, 193, 242, 42, 64, 134, 220, 180, 73, 220, 85, 182, 135, 120, 173, 162, 85, 9, 143, 255, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}