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: fa2f4304619762548b44fe79149ec89e9dafe4b47d7d62dc61027888dd820dfe
Tx prefix hash: be94af5ac3209d8fa62e4f0200a3d52cb55654a37ea7271989ca2b955797db69
Tx public key: 615aa65b12d5654dcafa91f18a9674b24d37897804f20dd87afdb205e59a1144
| Timestamp: 1779640429 | Timestamp [UTC]: 2026-05-24 16:33:49 | Age [y:d:h:m:s]: 00:015:11:05:01 |
| Block: 1292 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6655 | RingCT/type: yes/0 |
| Extra: 01615aa65b12d5654dcafa91f18a9674b24d37897804f20dd87afdb205e59a1144020900000002ba6d17be00 | ||
1 output(s) for total of 35.097841043186 HMNY
| stealth address | amount | amount idx | tag |
| 00: f4f865dd4dbe700fb195b3ecf0d14ce25b17853a186ccfb806463be2933eedd6 | 35.097841043186 | 1440 of 0 | <40> |
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": 1352,
"vin": [ {
"gen": {
"height": 1292
}
}
],
"vout": [ {
"amount": 35097841043186,
"target": {
"tagged_key": {
"key": "f4f865dd4dbe700fb195b3ecf0d14ce25b17853a186ccfb806463be2933eedd6",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 97, 90, 166, 91, 18, 213, 101, 77, 202, 250, 145, 241, 138, 150, 116, 178, 77, 55, 137, 120, 4, 242, 13, 216, 122, 253, 178, 5, 229, 154, 17, 68, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}