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: 5442609ae6fdd0c263788c43030d921ffbdcee83bc0a1584be521165316a423b
Tx prefix hash: 33567dc0faaf4ac8a7e91b6e1a1b42d5f5f6bb104da27feaae9aad8f5cff4d0f
Tx public key: af95c5ef727d8f96349b600f751ac5d7a9e3c1fe1c000782e161a08cc74732c9
| Timestamp: 1780052887 | Timestamp [UTC]: 2026-05-29 11:08:07 | Age [y:d:h:m:s]: 00:010:14:27:50 |
| Block: 4419 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3467 | RingCT/type: yes/0 |
| Extra: 01af95c5ef727d8f96349b600f751ac5d7a9e3c1fe1c000782e161a08cc74732c902090000000426697be300 | ||
1 output(s) for total of 34.889130544269 HMNY
| stealth address | amount | amount idx | tag |
| 00: ac526e110c758e7880e71aa689e0e96fc307df4e0c4a863d3eaed88375e528cc | 34.889130544269 | 5529 of 0 | <a5> |
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": 4479,
"vin": [ {
"gen": {
"height": 4419
}
}
],
"vout": [ {
"amount": 34889130544269,
"target": {
"tagged_key": {
"key": "ac526e110c758e7880e71aa689e0e96fc307df4e0c4a863d3eaed88375e528cc",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 175, 149, 197, 239, 114, 125, 143, 150, 52, 155, 96, 15, 117, 26, 197, 215, 169, 227, 193, 254, 28, 0, 7, 130, 225, 97, 160, 140, 199, 71, 50, 201, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}