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: 04392969fbfff63087d294488aba3fe8bfac86bf4d9158e845f06f223c445d33
Tx prefix hash: 4e7cd4498e190a7a711582fd77b86fe3dbf27f83255329c98b79e84373f85956
Tx public key: ebdd45bf02fd8629556e179adb0b78c4fc187076265292353b6ae62f59cd66f1
| Timestamp: 1780025173 | Timestamp [UTC]: 2026-05-29 03:26:13 | Age [y:d:h:m:s]: 00:011:00:12:37 |
| Block: 4166 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3783 | RingCT/type: yes/0 |
| Extra: 01ebdd45bf02fd8629556e179adb0b78c4fc187076265292353b6ae62f59cd66f102090000000126697be300 | ||
1 output(s) for total of 34.905970694254 HMNY
| stealth address | amount | amount idx | tag |
| 00: 80de41f8d19a1e47b1fa31ee5d9a924a031dee8da038d9eefd3aa96363df0082 | 34.905970694254 | 5199 of 0 | <91> |
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": 4226,
"vin": [ {
"gen": {
"height": 4166
}
}
],
"vout": [ {
"amount": 34905970694254,
"target": {
"tagged_key": {
"key": "80de41f8d19a1e47b1fa31ee5d9a924a031dee8da038d9eefd3aa96363df0082",
"view_tag": "91"
}
}
}
],
"extra": [ 1, 235, 221, 69, 191, 2, 253, 134, 41, 85, 110, 23, 154, 219, 11, 120, 196, 252, 24, 112, 118, 38, 82, 146, 53, 59, 106, 230, 47, 89, 205, 102, 241, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}