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: f2d8f720e445cec68c7974b55ab33d983df5c57af4b90c221844544c1dd98997
Tx prefix hash: 029fd06a77b071a8321d8adcd5d83ddfd631d1e13669cb5c90a811a26466536b
Tx public key: c5666b64ce080a4ac5c8ad0285ce6fcc0dde17f0b4d2f9721c340673f3ef92c5
| Timestamp: 1779794434 | Timestamp [UTC]: 2026-05-26 11:20:34 | Age [y:d:h:m:s]: 00:013:15:20:02 |
| Block: 2256 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5641 | RingCT/type: yes/0 |
| Extra: 01c5666b64ce080a4ac5c8ad0285ce6fcc0dde17f0b4d2f9721c340673f3ef92c502090000000426697be300 | ||
1 output(s) for total of 35.040766832443 HMNY
| stealth address | amount | amount idx | tag |
| 00: af2d3735c63d57b13babd0ff258f5cdad99d644d182df7a71f0744f132840ff4 | 35.040766832443 | 2618 of 0 | <64> |
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": 2316,
"vin": [ {
"gen": {
"height": 2256
}
}
],
"vout": [ {
"amount": 35040766832443,
"target": {
"tagged_key": {
"key": "af2d3735c63d57b13babd0ff258f5cdad99d644d182df7a71f0744f132840ff4",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 197, 102, 107, 100, 206, 8, 10, 74, 197, 200, 173, 2, 133, 206, 111, 204, 13, 222, 23, 240, 180, 210, 249, 114, 28, 52, 6, 115, 243, 239, 146, 197, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}