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: 9908fc3323372e0ddd6ccde3dee7a07bb6849aaaad745ffe9f5332c0db7c4823
Tx prefix hash: cf73c932a57576fd8900032789a7efce12844e9bee11abde90834307e0237150
Tx public key: eeeb1f4bf7ff91471045345a5a374a61797e8d88308d1cc36d0f747780a6f137
| Timestamp: 1779437750 | Timestamp [UTC]: 2026-05-22 08:15:50 | Age [y:d:h:m:s]: 00:018:08:53:13 |
| Block: 174 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8561 | RingCT/type: yes/0 |
| Extra: 01eeeb1f4bf7ff91471045345a5a374a61797e8d88308d1cc36d0f747780a6f137020900000002a662ed0300 | ||
1 output(s) for total of 35.172764159650 HMNY
| stealth address | amount | amount idx | tag |
| 00: bcb0fab9c4934e3ae548c5bc583a1ab5d2bedae24f88d57292a9d629e53b0fab | 35.172764159650 | 170 of 0 | <40> |
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": 234,
"vin": [ {
"gen": {
"height": 174
}
}
],
"vout": [ {
"amount": 35172764159650,
"target": {
"tagged_key": {
"key": "bcb0fab9c4934e3ae548c5bc583a1ab5d2bedae24f88d57292a9d629e53b0fab",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 238, 235, 31, 75, 247, 255, 145, 71, 16, 69, 52, 90, 90, 55, 74, 97, 121, 126, 141, 136, 48, 141, 28, 195, 109, 15, 116, 119, 128, 166, 241, 55, 2, 9, 0, 0, 0, 2, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}