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: cd03fb419d6302f5faf276f6ccbc160a986408f4f2318a839e58dea7a1ed105d
Tx prefix hash: 6431d32fd568459135e2cce6ae7c0158d3f5092a48cce4bc9691c497d602b76e
Tx public key: c0f57efafcc5054bf7cf590ffb3cbbd70114a65038b7c07fc1a5c2e29b3b2b76
| Timestamp: 1779715036 | Timestamp [UTC]: 2026-05-25 13:17:16 | Age [y:d:h:m:s]: 00:014:11:29:31 |
| Block: 1625 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6261 | RingCT/type: yes/0 |
| Extra: 01c0f57efafcc5054bf7cf590ffb3cbbd70114a65038b7c07fc1a5c2e29b3b2b76020900000001ba6d17be00 | ||
1 output(s) for total of 35.075555808113 HMNY
| stealth address | amount | amount idx | tag |
| 00: 24915f696df96c19ce05ef6757c371c0fa381cd240cbfe6fe76371a84b400139 | 35.075555808113 | 1783 of 0 | <2e> |
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": 1685,
"vin": [ {
"gen": {
"height": 1625
}
}
],
"vout": [ {
"amount": 35075555808113,
"target": {
"tagged_key": {
"key": "24915f696df96c19ce05ef6757c371c0fa381cd240cbfe6fe76371a84b400139",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 192, 245, 126, 250, 252, 197, 5, 75, 247, 207, 89, 15, 251, 60, 187, 215, 1, 20, 166, 80, 56, 183, 192, 127, 193, 165, 194, 226, 155, 59, 43, 118, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}