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: f157677807b2935e3963df0fe589a3f5ce7786f71aa687f55ac22e96cc66d1ea
Tx prefix hash: d3802419de453fa23cfa212151a15a4834857c12cf78cf821b73cc8143ccc200
Tx public key: 852d5e84f7fc18ed4493b6a8051f295e0e710df6092327e42d3081091307c498
| Timestamp: 1779630619 | Timestamp [UTC]: 2026-05-24 13:50:19 | Age [y:d:h:m:s]: 00:015:11:45:38 |
| Block: 880 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7006 | RingCT/type: yes/0 |
| Extra: 01852d5e84f7fc18ed4493b6a8051f295e0e710df6092327e42d3081091307c498020900000001ba6d17be00 | ||
1 output(s) for total of 35.125432762728 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1902527c543fff54d69c463e00c3eeb439c3f39442e2e74fc84c9111151a28b8 | 35.125432762728 | 1012 of 0 | <37> |
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": 940,
"vin": [ {
"gen": {
"height": 880
}
}
],
"vout": [ {
"amount": 35125432762728,
"target": {
"tagged_key": {
"key": "1902527c543fff54d69c463e00c3eeb439c3f39442e2e74fc84c9111151a28b8",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 133, 45, 94, 132, 247, 252, 24, 237, 68, 147, 182, 168, 5, 31, 41, 94, 14, 113, 13, 246, 9, 35, 39, 228, 45, 48, 129, 9, 19, 7, 196, 152, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}