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: ba66363230578da0cd338bdb969d83e580003d7f02d3c06b1428e507225bac2c
Tx prefix hash: 2498ca2b162df703fbacf8df84f7ec3486fc4f83e57a88b471baa0989b0a1229
Tx public key: 8bb575c33c005607f5877c859c6e30ba65be9b3e54484a424875571e449f2fae
| Timestamp: 1779436925 | Timestamp [UTC]: 2026-05-22 08:02:05 | Age [y:d:h:m:s]: 00:017:15:16:48 |
| Block: 152 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7734 | RingCT/type: yes/0 |
| Extra: 018bb575c33c005607f5877c859c6e30ba65be9b3e54484a424875571e449f2fae020900000001a662ed0300 | ||
1 output(s) for total of 35.174240099944 HMNY
| stealth address | amount | amount idx | tag |
| 00: 10fc42c7045390c20ff6d81ef687f471adc7a8701c19116d6d2fcaa47a6ab517 | 35.174240099944 | 148 of 0 | <de> |
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": 212,
"vin": [ {
"gen": {
"height": 152
}
}
],
"vout": [ {
"amount": 35174240099944,
"target": {
"tagged_key": {
"key": "10fc42c7045390c20ff6d81ef687f471adc7a8701c19116d6d2fcaa47a6ab517",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 139, 181, 117, 195, 60, 0, 86, 7, 245, 135, 124, 133, 156, 110, 48, 186, 101, 190, 155, 62, 84, 72, 74, 66, 72, 117, 87, 30, 68, 159, 47, 174, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}