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: 52d28e3751b10d7fdba2cc12625af500a8854e1e57e53180f499af54c17dd076
Tx prefix hash: ce23753eafe282d6480be8f8eb51f011886303bbfb76114ea14b97fdfc677fed
Tx public key: 90ed2b01d71b00168b325db79930b9edc992628839b0d8666f0fe4b6fcec3aea
| Timestamp: 1780129757 | Timestamp [UTC]: 2026-05-30 08:29:17 | Age [y:d:h:m:s]: 00:009:19:21:41 |
| Block: 4931 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3036 | RingCT/type: yes/0 |
| Extra: 0190ed2b01d71b00168b325db79930b9edc992628839b0d8666f0fe4b6fcec3aea02090000000426697be300 | ||
1 output(s) for total of 34.855075726280 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5728e23ed9e485a117d0b9d7727b4eb05faa29946854d6dd55d282c2e9f25bab | 34.855075726280 | 6262 of 0 | <d7> |
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": 4991,
"vin": [ {
"gen": {
"height": 4931
}
}
],
"vout": [ {
"amount": 34855075726280,
"target": {
"tagged_key": {
"key": "5728e23ed9e485a117d0b9d7727b4eb05faa29946854d6dd55d282c2e9f25bab",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 144, 237, 43, 1, 215, 27, 0, 22, 139, 50, 93, 183, 153, 48, 185, 237, 201, 146, 98, 136, 57, 176, 216, 102, 111, 15, 228, 182, 252, 236, 58, 234, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}