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: 56a48e60a0be9eda2cb273c132701b2ea45bd3a401c945f5c61e2620c32c7ddb
Tx prefix hash: 7a6a484d43d65e75c1e901d267706de9d4f978187d866c65e843b0c9f765d223
Tx public key: 188da16bdc109ef115b12357c92574719b2f848a18a1dbc03946c84701ce9968
| Timestamp: 1779458347 | Timestamp [UTC]: 2026-05-22 13:59:07 | Age [y:d:h:m:s]: 00:017:11:36:50 |
| Block: 410 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7476 | RingCT/type: yes/0 |
| Extra: 01188da16bdc109ef115b12357c92574719b2f848a18a1dbc03946c84701ce996802090000000693369e7d00 | ||
1 output(s) for total of 35.156935240614 HMNY
| stealth address | amount | amount idx | tag |
| 00: 08ea6b202e63fefa0eeed108f35647db1ffc78fe804c0cd1d1ac0aee9baf58c6 | 35.156935240614 | 412 of 0 | <d8> |
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": 470,
"vin": [ {
"gen": {
"height": 410
}
}
],
"vout": [ {
"amount": 35156935240614,
"target": {
"tagged_key": {
"key": "08ea6b202e63fefa0eeed108f35647db1ffc78fe804c0cd1d1ac0aee9baf58c6",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 24, 141, 161, 107, 220, 16, 158, 241, 21, 177, 35, 87, 201, 37, 116, 113, 155, 47, 132, 138, 24, 161, 219, 192, 57, 70, 200, 71, 1, 206, 153, 104, 2, 9, 0, 0, 0, 6, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}