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: 9c4e0cf003923fbf1ab84ef40815297b7a1c77d9efc9a33a388bb7f8a57a5d18
Tx prefix hash: f8b03c35d53f5cc897751cffdc833207be04afd4ca4f4d218b1ceb0db071031b
Tx public key: 65783d42e0d17d72e23de25a8d7ae3fb8351f901e224c5aa91f8769634a2c64a
| Timestamp: 1780014427 | Timestamp [UTC]: 2026-05-29 00:27:07 | Age [y:d:h:m:s]: 00:011:01:08:50 |
| Block: 4112 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3774 | RingCT/type: yes/0 |
| Extra: 0165783d42e0d17d72e23de25a8d7ae3fb8351f901e224c5aa91f8769634a2c64a02090000000526697be300 | ||
1 output(s) for total of 34.909566087033 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3224c185cc5af1c0b0b994ba67658593bd23a9e21cc25673e254faa4df4799c2 | 34.909566087033 | 5125 of 0 | <10> |
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": 4172,
"vin": [ {
"gen": {
"height": 4112
}
}
],
"vout": [ {
"amount": 34909566087033,
"target": {
"tagged_key": {
"key": "3224c185cc5af1c0b0b994ba67658593bd23a9e21cc25673e254faa4df4799c2",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 101, 120, 61, 66, 224, 209, 125, 114, 226, 61, 226, 90, 141, 122, 227, 251, 131, 81, 249, 1, 226, 36, 197, 170, 145, 248, 118, 150, 52, 162, 198, 74, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}