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: 6f253624fa07f74e4950550bbf4ed869830078034db3a5e38ea194150b6663fb
Tx prefix hash: 33ba40fcb5c50e7b131b5c75e05c19955c2051790c29abe727e1e4347f8ae918
Tx public key: 4b9d5f257aa16f7ff0fe5fef7dff442dbc8c51a295821461157b07d75b04db75
| Timestamp: 1779845310 | Timestamp [UTC]: 2026-05-27 01:28:30 | Age [y:d:h:m:s]: 00:013:00:07:27 |
| Block: 2442 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5444 | RingCT/type: yes/0 |
| Extra: 014b9d5f257aa16f7ff0fe5fef7dff442dbc8c51a295821461157b07d75b04db7502090000000326697be300 | ||
1 output(s) for total of 35.028343948071 HMNY
| stealth address | amount | amount idx | tag |
| 00: a7736f77c56d3b1c1f2a9bad7bf44b00a85760aa6080ea1dc80ec21aad59ef9e | 35.028343948071 | 2870 of 0 | <e9> |
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": 2502,
"vin": [ {
"gen": {
"height": 2442
}
}
],
"vout": [ {
"amount": 35028343948071,
"target": {
"tagged_key": {
"key": "a7736f77c56d3b1c1f2a9bad7bf44b00a85760aa6080ea1dc80ec21aad59ef9e",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 75, 157, 95, 37, 122, 161, 111, 127, 240, 254, 95, 239, 125, 255, 68, 45, 188, 140, 81, 162, 149, 130, 20, 97, 21, 123, 7, 215, 91, 4, 219, 117, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}